Repository navigation
Conversation
Owner
Author
|
The isolated failure is now covered by xgo-dev#2461, and R11 carries that fix as a separate temporary dependency commit for validation. Closing this diagnostics-only draft; the branch remains available for the investigation history. |
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
1 participant
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.
Temporary diagnostic PR based on #211.
The full R11 matrix showed one reproducible hang: the Windows MinGW/386
c-archiveC consumer enters the exported Go library successfully, printsHello, World!, and then stops while eight foreign Windows threads exercise fault continuation and repeatedFormatValuecalls. The equivalentc-sharedconsumer passes.This PR adds one narrow workflow that builds and runs only that static consumer. The diagnostic consumer records each thread's progress before and after fault continuation and each Go export call, replaces the unbounded wait with a 45-second diagnostic timeout, and aborts with all progress counters so the runner cannot remain occupied for an hour.
This PR is not intended to merge. Once the failing boundary is identified, only the minimal runtime/compiler fix and permanent regression test will be moved to R11.