-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testCheckpoint takes unreasonably long to fail #516
Comments
I can provoke this with this hack: --- test/verify/check-networking-checkpoints
+++ test/verify/check-networking-checkpoints
@@ -43,6 +43,7 @@ class TestNetworking(NetworkCase):
b.wait_visible("#network-interface")
# Disconnect
+ m.spawn("sleep 5; systemctl stop NetworkManager", "kill-nm")
self.wait_onoff(".panel-heading:contains('%s')" % iface, True)
self.toggle_onoff(".panel-heading:contains('%s')" % iface)
The The most direct way to catch this is: --- test/verify/check-example
+++ test/verify/check-example
@@ -36,6 +36,9 @@ class TestExample(MachineCase):
def testBasic(self):
self.login_and_go("/system")
+ def testNetKaputt(self):
+ self.machine.spawn("sleep 2; ip link set eth0 down", "kill-net")
+ self.assertTrue(False)
class TestPersistentExample(PersistentMachineCase):
This also explains why the journal logs in that test are all 0 bytes. |
Hah, this is a bug in bots, |
martinpitt
added a commit
to martinpitt/bots
that referenced
this issue
Feb 10, 2020
This caused tests hanging for half an hour on e. g. cleanup commands like calling "journalctl" in cockpit's `BaseCase.copy_journal()`. Fixes cockpit-project#516
Fixed in #517 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This rhel-8-2-distropkg test run timed out, due to
I. e. these three retries took 1½ hours. There is clearly a broken test retry loop somewhere.
The text was updated successfully, but these errors were encountered: