-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
docs: update docs versions 6.8.16 #25839
Conversation
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Steps errorsExpand to view the steps failures
|
/test |
1 similar comment
/test |
/test |
2 similar comments
/test |
/test |
it looks like the following command never ends, it is running for more than 2h 30min, and in the last 2 hours there is no log output, I guess is stuck.
|
/test |
The hung test is Auditbeat's I think this may be caused by the same issue we're suffering in some cloud workers, which causes some ubuntu 16&18 workers to get stuck when a process tries to use netlink/auditd. For now I will re-run the tests hoping that a different worker gets picked. @kuisathaverat I suggest to revert the extended timeout in 9fd5d6b. |
/test |
I just update the pipeline to use Ubuntu 20.04, let's see how it works |
f4e096f
to
499436c
Compare
After more investigation we've came to the conclusion that the CI problem is caused by an Auditbeat service running in the workers, that's suffering from the bug described in #26031 and fixed by #26032. For now we can just merge this ignoring the Auditbeat failures, we'll try to have the Auditbeat services updated in our infrastructure when the above PR gets merged. |
@andresrc it's not necessary, the problem is caused by an Auditbeat 7.8 running in the test workers, managed by infra, not by the Auditbeat that is built from the 6.8 branch and used during tests. |
Updates docs versions to 6.8.16.
Merge before the final Release build.