-
Notifications
You must be signed in to change notification settings - Fork 129
build-sys: Work around #1546 #1547
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a temporary workaround to address an issue with the base image by removing the /root/buildinfo
directory before running container lints. The change is straightforward and seems correct for its purpose. I have one suggestion to improve the comment to make it easier to track and remove this workaround in the future.
While we work to fix the base image (again). Signed-off-by: Colin Walters <walters@verbum.org>
ded6023
to
926dec1
Compare
re: c10s aarch64 failure - #1544 (comment) 🤔 |
The previous locking code was just wrong; my bad for not stress testing it. Fix it an add a test too. Signed-off-by: Colin Walters <walters@verbum.org>
Since we now have two different things breaking our CI, I've rolled a fix for the locking into this PR. |
async_task_with_spinner("Waiting for sysroot lock...", sysroot.lock_future()).await?; | ||
let sysroot_clone = sysroot.clone(); | ||
let locker = tokio::task::spawn_blocking(move || sysroot_clone.lock()); | ||
async_task_with_spinner("Waiting for sysroot lock...", locker).await??; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does for me basically always cause a flicker of "Waiting for sysroot lock..." on a terminal, but if someone cares we can change that.
While we work to fix the base image (again).
Closes: #1544