-
Notifications
You must be signed in to change notification settings - Fork 763
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
Reg-tests timeouts #2562
Comments
Please note that there have been chaotic versions which could possibly not leave immediately, so it's not completely impossible that you've faced one of them. I'd say that if this continues to happen with latest -dev then it's a real concern, otherwise it's perfectly possible that it has since been fixed. |
It does happen at least up to 03ca16f here (see https://gitlab.com/mangadex-pub/haproxy/-/jobs/6785851604).
I just reported the first "faulty" (if the issue is not fully on my side) commit I found in my build history. That said, looking at this repo's GH Actions doesn't seem to show the same issue, so I'm not sure yet if it's legitimate. |
Interestingly, it doesn't happen in my GH Actions either (see: https://github.com/mangadex-pub/haproxy/actions/runs/8989710831/job/24693449238), so it is most likely dependency on some system permissions for something in those tests. Permissions which we presumably don't grant to containers in our k8s cluster running Gitlab CI pipelines. |
Tool Name and Version
N/A
Code Report
Additional Information
As I was bisecting for #2561, I noticed that my builds took much longer to finish (an extra 5-6 minutes).
After having a look, it seems that the cause is a few regtests regularly failing with timeouts (see above), which was not the case in 7151076 but is the case in e158b7e.
It is suspicious as my build environment/options are not very original. I'll investigate after my bisecting is done, but this issue will do as a reminder.
for reference:
Output of
haproxy -vv
The text was updated successfully, but these errors were encountered: