windows-amd64 tests flaky: TestGcPacer, TestCgoPanicCallback, TestBigStackCallbackCgo, ...
Open
Nobody has claimed this yet.
Flaky
Test
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
=== Failed
=== FAIL: runtime TestCallbackInAnotherThread (0.14s)
=== FAIL: runtime TestCgoPanicCallback (unknown)
=== FAIL: runtime TestBigStackCallbackCgo (unknown)
=== FAIL: runtime TestGcPacer/Steady (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrAlignmentNoPtr (unknown)
=== FAIL: runtime TestGcPacer/OscAlloc (unknown)
=== FAIL: runtime TestNetpollDeadlock (unknown)
=== FAIL: runtime TestCheckPtr (unknown)
=== FAIL: runtime TestGcPacer/StepScannableFrac (unknown)
=== FAIL: runtime TestRecoverBeforePanicAfterGoexit (unknown)
=== FAIL: runtime TestGcPacer (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrSliceFail (unknown)
=== FAIL: runtime TestCheckPtr2 (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrArithmetic2 (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrSmall (unknown)
=== FAIL: runtime TestRecoverBeforePanicAfterGoexit2 (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrAlignmentPtr (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrAlignmentNilPtr (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrSliceOK (unknown)
=== FAIL: runtime TestGcPacer/JitterAlloc (unknown)
=== FAIL: runtime TestVDSO (unknown)
=== FAIL: runtime TestGcPacer/StepAlloc (unknown)
=== FAIL: runtime TestGcPacer/HeavyJitterAlloc (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrArithmetic (unknown)
=== FAIL: runtime TestGcPacer/HeavyStepAlloc (unknown)
=== FAIL: runtime TestPanicTraceback (unknown)
=== FAIL: runtime TestCheckPtr/CheckPtrSize (unknown)
I'm not sure if there's a common thread connecting these tests. 😕
Some failures are shared with:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Azure build logs and compare the listed runtime failures, including TestGcPacer, TestCheckPtr, and the cgo callback tests. Review the related microsoft/go issue #251 for overlap. Done means identifying whether the failures share a cause and documenting or addressing a reproducible Windows-amd64 failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100