kola testiso tests on f41+ sometimes time out #1796
Labels
pipeline failure
This issue or pull request is derived from CI failures
Comments
|
FTR I did look at the code the other day to assure that if the process was killed it should print out a message to the console. I tested that today and it seems true: killed the qemu process with a |
dustymabe
added a commit
to dustymabe/fedora-coreos-pipeline
that referenced
this issue
Sep 20, 2024
We're trying to get more information on the root cause for coreos/fedora-coreos-tracker#1796 and maybe this will help us find a clue.
|
Saw this again today in CI for coreos/fedora-coreos-config#3171 Opened coreos/fedora-coreos-pipeline#1039 to see if we can get more information about the problem. |
jlebon
pushed a commit
to coreos/fedora-coreos-pipeline
that referenced
this issue
Sep 20, 2024
We're trying to get more information on the root cause for coreos/fedora-coreos-tracker#1796 and maybe this will help us find a clue.
marmijo
added
the
pipeline failure
|
Saw this again today in bodhi tests for https://bodhi.fedoraproject.org/updates/FEDORA-2024-5a61a2fa45 Unfortunately coreos/fedora-coreos-pipeline#1039 doesn't help us here because that isn't used in those CI tests. |
jlebon
added a commit
to jlebon/coreos-ci
that referenced
this issue
Oct 29, 2024
This matches what we do in the pipeline. Motivated by wanting to get to the bottom of coreos/fedora-coreos-tracker#1796, which happens often in the Bodhi tests.
dustymabe
pushed a commit
to coreos/coreos-ci
that referenced
this issue
Oct 29, 2024
This matches what we do in the pipeline. Motivated by wanting to get to the bottom of coreos/fedora-coreos-tracker#1796, which happens often in the Bodhi tests.
dustymabe
added a commit
to dustymabe/coreos-assembler
that referenced
this issue
Nov 1, 2024
Otherwise only `info` level messages will go to the console of the machine. We were digging into a new instance of [1] and found that we weren't really getting debug messages on the console of the machine (which means no new clues as to why the tests are timing out). Turns out this is why we weren't getting those new debug messages we thought we would get. [1] coreos/fedora-coreos-tracker#1796
dustymabe
added a commit
to coreos/coreos-assembler
that referenced
this issue
Nov 1, 2024
Otherwise only `info` level messages will go to the console of the machine. We were digging into a new instance of [1] and found that we weren't really getting debug messages on the console of the machine (which means no new clues as to why the tests are timing out). Turns out this is why we weren't getting those new debug messages we thought we would get. [1] coreos/fedora-coreos-tracker#1796
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've seen this a couple of times in the Bodhi testing, but now it also showed up in next-devel:
But the system logs don't show anything weird. Almost like either QEMU was killed, or kola just lost contact with it. Pod has 9Gi of RAM and testiso tests run serially so memory limits shouldn't be a concern here.
pxe-offline-install.bios.zip
The text was updated successfully, but these errors were encountered: