-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
test: wait for interfaces online #19881
Conversation
(I do not check this work or not.) cc @bluca. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good in principle, given the failure does not happen often let's see if this helps
SemaphoreCI's unhappy:
|
00b0a47
to
d347e2c
Compare
Now, semaphore is green. Setting the green label again. |
bionic-s390x: looks possibly related:
About the commit message: please say why the change is done, instead of just linking to an online discussion. |
@bluca How can I get the journal of the failed CI results?? |
it's documented in the README in the test/ subfolder - get the link from the CI status here, and change log.gz with artifacts.tar.gz |
@bluca Oh, it is documented!? I did not know that. Thanks! |
Hmm, it does not contain anything about networkd-test.py failure... |
Ah yes you are indeed right - that's because we don't collect any info about that test. For the "upstream" suite for example, we explicitly extract the journal files (you can see them in the "artifacts" directory of the tarball".
|
Hmm, I noticed that the issue can be found only on s390x... So, the issue is not a simple(?) timing issue. |
Prompted by #19811 (comment).