Skip to content
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

Closed
mudler opened this issue Jul 1, 2021 · 4 comments
Closed

ci: sporadic failures "Exit 127" #356

mudler opened this issue Jul 1, 2021 · 4 comments
Labels
kind/bug Something isn't working

Comments

@mudler
Copy link
Contributor

mudler commented Jul 1, 2021

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 now

To 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

@mudler mudler added the kind/bug Something isn't working label Jul 1, 2021
@mudler mudler assigned mudler and unassigned mudler Jul 1, 2021
@davidcassany
Copy link
Contributor

I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it:

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 make deps step. If the issue disappears without it I'd say we have to forget about UPX until it gets fixed upstream.

@mudler
Copy link
Contributor Author

mudler commented Jul 1, 2021

I suspect it's due to part of our binaries (luet and extensions) compressed with UPX. See also upstream issues about it:

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 make deps step. If the issue disappears without it I'd say we have to forget about UPX until it gets fixed upstream.

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 --brute is causing issues

mudler added a commit that referenced this issue Jul 2, 2021
mudler added a commit that referenced this issue Jul 2, 2021
@mudler
Copy link
Contributor Author

mudler commented Jul 5, 2021

I think we can close this for now and re-open it if needed, doesn't seems happening anymore after disabling upx

@mudler mudler closed this as completed Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants