Repository navigation
issues: a test build waited forty minutes on its own process's sysroot lock - #1142
Merged
Merged
Conversation
…t lock Observed in one QEMU run of #1077's branch; the cause is not established. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records a harness defect observed while verifying #1077, with its cause unknown ("No silent debt").
During one
cargo test --test toyos-buildrun of eight guest tests at929e73d6c, one guest build waited 2611 s on a sysroot lock held by its own test process. Six other builds waiting on the same lock went on once the sysroot was built. The run had to be killed. A neighbouring guest build failed to compile just before, but that is not established as the cause. The record has the timeline, the masked log at its evidence commit, an exit and an owner.Markdown only: there is no build or test to run. The check is consistency with
issues/README.md's frontmatter and format.🤖 Generated with Claude Code