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
(@hawkw's dbg!() in the tests is immediately validated because the print at 1490 rules out any of the other earlier instance_wait_for_state, nice)
this log looks like the expect_instance_reboot_fail just before the fated instance_wait_for_state, but it looks like everything is in a reasonable state. i think what happened here is that, just before we'd instance_wait_for_state, the reincarnation background task ran (see here) and reincarnated the instance. then the instance was Running so we'd never reach Failed in instance_wait_for_state() because Nexus kind of beat us to running the tail end of this test.
@hawkw i'm mostly not sure if background tasks would run themselves in tests like this, does that sound right? maybe we should have the test look for Failed or Running, and if it's already Running we instead assume the background task independently ran and did what we wanted?
The text was updated successfully, but these errors were encountered:
This test failed on a CI run on 5b6db25 (imminently a PR, just not one yet):
This is the runs page, though I reran the failed job because.. well, it's a flake: https://github.com/oxidecomputer/omicron/runs/41756574687
Buildomat from the failed run though: https://buildomat.eng.oxide.computer/wg/0/details/01JTKR9B4DY2HPFFKKXH60N0QC/2WSRkGyhWpcAbSCPmZLleIzTW0fVbYxTlNQrx6qWIENCOeiz/01JTKR9SBGS5SP7K0ZHFM64VJ6 .
Log showing the specific test failure:
https://buildomat.eng.oxide.computer/wg/0/details/01JTKR9B4DY2HPFFKKXH60N0QC/2WSRkGyhWpcAbSCPmZLleIzTW0fVbYxTlNQrx6qWIENCOeiz/01JTKR9SBGS5SP7K0ZHFM64VJ6#S7310
Excerpt from the log showing the failure:
which is to say that this expected transition to Failed didn't happen within 120s: https://github.com/oxidecomputer/omicron/blob/ef01db1/nexus/tests/integration_tests/instances.rs#L1518-L1522
(@hawkw's
dbg!()
in the tests is immediately validated because the print at 1490 rules out any of the other earlierinstance_wait_for_state
, nice)this log looks like the
expect_instance_reboot_fail
just before the fatedinstance_wait_for_state
, but it looks like everything is in a reasonable state. i think what happened here is that, just before we'dinstance_wait_for_state
, the reincarnation background task ran (see here) and reincarnated the instance. then the instance was Running so we'd never reach Failed ininstance_wait_for_state()
because Nexus kind of beat us to running the tail end of this test.@hawkw i'm mostly not sure if background tasks would run themselves in tests like this, does that sound right? maybe we should have the test look for Failed or Running, and if it's already Running we instead assume the background task independently ran and did what we wanted?
The text was updated successfully, but these errors were encountered: