Repository navigation
Conversation
Author
|
Control read: dispatched build-cpu.yml on this branch (run 38132058259) and on #52's (38132059593) at the same hour; windows/x64-openblas passed on both, so #52's two test-thread-safety 0xc0000374 crashes were intermittent, not specific to #52. Closing the control; the branch had no change to merge. |
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.
Empty commit on master (af1a3c9), for an A/B against #52: #52 failed
test-thread-safety(0xc0000374, heap corruption) on windows/x64-openblas at both of its heads, while #49–#51 passed. The test never reaches #52's code, and passes 5 of 5 locally (CUDA build, CPU path). This draft runs the same CI on the same runners today. I'll close it once the result is read.🤖 Generated with Claude Code