-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
CircleCI not able to build Coreboot 4.8.1 after bullseye docker image change #807
Comments
Same happened back there at that commit from CircleCI |
what was the resolution when the issue first surfaced back then? |
The following successful tests were to test 4.12. This commit broke 4.8.1 builds on CircleCI from there and on. I'm trying this https://app.circleci.com/pipelines/github/tlaurion/heads/316/workflows/d636d5c4-d490-40c3-bfab-ac5e4aee95b5/jobs/344 |
https://app.circleci.com/pipelines/github/tlaurion/heads/319/workflows/e04e0993-5745-4585-9891-b78cd8b9822f/jobs/347 implements #799 (comment) and pass the failing point of the current build. @MrChromebox can you take a look at https://github.com/osresearch/heads/compare/master...tlaurion:make_421_fix-CircleCI_unhack?expand=1#diff-8d39c7575f026b40d86f213a4fcea2d6 and advise? |
@MrChromebox https://github.com/osresearch/heads/compare/master...tlaurion:make_421_fix-CircleCI_unhack?expand=1#diff-8d39c7575f026b40d86f213a4fcea2d6 Fails at :
Where continues with:
|
@MrChromebox tlaurion@51a0de3, being a revert of the condition actually failing has passed the point where past condition failed. |
@MrChromebox reverting here to test build.... I'm really confused. |
@MrChromebox : culprit is bullseye docker image change... Might need more investigation. Reverted to docker:10 docker image in #808 |
Fixed under #808 |
@MrChromebox
Building without cache since (EDIT:) commit 9eff5c5 results in:
Any idea?
The text was updated successfully, but these errors were encountered: