You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2024. It is now read-only.
Sometimes test runs fail because there is an issue with a host in Beaker. We need to detect such conditions to avoid sending such failures to developers.
One way to do that would be running tests with a known-good kernel on the same host after a failure is detected. If that fails as well, we can assume that the host is at fault. Otherwise, we can assume that it's a genuine test failure.
We can implement the above by passing a URL of a known-good kernel to skt's Beaker runner, and the known-good kernel can be the baseline the patches are applied to. Sktm would need to be in control of, or at least know, the kernel locations before it can do that.
Also check the (now non-)existing logic in case there are some extra smarts we can use.
The text was updated successfully, but these errors were encountered:
Sometimes test runs fail because there is an issue with a host in Beaker. We need to detect such conditions to avoid sending such failures to developers.
One way to do that would be running tests with a known-good kernel on the same host after a failure is detected. If that fails as well, we can assume that the host is at fault. Otherwise, we can assume that it's a genuine test failure.
We can implement the above by passing a URL of a known-good kernel to skt's Beaker runner, and the known-good kernel can be the baseline the patches are applied to. Sktm would need to be in control of, or at least know, the kernel locations before it can do that.
Also check the (now non-)existing logic in case there are some extra smarts we can use.
The text was updated successfully, but these errors were encountered: