-
Notifications
You must be signed in to change notification settings - Fork 53
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
ci: sporadic failures "Exit 127" #356
Comments
If so I'd suggest to add a toggle to use UPX or not and then just give it a try for some time without. On CI this happens quite often, I mostly saw it on |
I do agree, but I would give a deeper look as we could also try to downgrade upx/upx#225 (comment) or try to use a different upx option, I think |
See #356 Signed-off-by: Ettore Di Giacinto <[email protected]>
See #356 Signed-off-by: Ettore Di Giacinto <[email protected]>
I think we can close this for now and re-open it if needed, doesn't seems happening anymore after disabling upx |
cos-toolkit version:
Not relevant
CPU architecture, OS, and Version:
Describe the bug
Sporadically CI fails with
ERRO[0000] fatal error: exit status 127
or more generically with exit status 127 in different places. This is happening very frequently, and becomes more noticeable nowTo Reproduce
Happened to me locally too (only once). My guess is a simple looping on the binaries generated with UPX will eventually fail with the above
Expected behavior
To not fail
Logs
Additional context
I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it: upx/upx#385 upx/upx#224 upx/upx#225 .
I'll use this issue to track all the occurences
The text was updated successfully, but these errors were encountered: