#12151 debug prints and random instrumentation to point at OS bug #12162
Conversation
This file contains 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
|
(It doesn't actually fix the issue, but I wanted to put the code somewhere.) |
|
Maybe it helps. I have pushed a chagne to GitHub action to allow you to connect to a specific run by using the GitHub Acions "debug" feature just click re-run on a job
And then select "Enable debug logging"
The GitHub Actions GUI is designed for loggin, but you can hijack it to make it easy to connect to the runner I find this useful when investigating test that fail on GitHub but pass on my system. You can login, and look arround the VM and check what's going on I hope it helps, feel free to revert the change |
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.
Scope and purpose
Fixes #12151