-
Notifications
You must be signed in to change notification settings - Fork 10
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
For unknown reason, when building with systemd-nspawn jobs exit as fatal even though they're not failing #122
Comments
@jonesmz Have you came across this issue? A quite few of the jobs "fail" and it has to be re-started. |
No, i have not seen what you're describing. But aren't these actually failing?
|
Technically ebuilds are but eix is not. |
What's the actual exit code from eix? |
How would I know that? |
eix is almost certainly exiting with a non-0 exit code, and that's why systemd-nspawn is terminating. |
No, it would appear to not be systemd-nspawn but rather the python portion itself. Read it fully. |
eix-sync returns non-zero, so systemd-nspawn returns non-zero, so build.dist stops |
I don't know why this happens but apperantly this is fatal for no reason?
Building the GenPi64OpenRC target.
The text was updated successfully, but these errors were encountered: