microsoft / microsoft/go

windows-amd64 tests flaky (cgo and others)

Open
#251 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Flaky Test
Dominant language
Go
Stars
431
Forks
44
Avg merge
21h 18m
Merged PRs (30d)
30

Description

https://dev.azure.com/dnceng/internal/_build/results?buildId=1450673&view=results hit:

=== Failed
=== FAIL: runtime TestSyscallN/arg-6 (unknown)
=== FAIL: runtime TestSyscallN/arg-1 (unknown)
=== FAIL: runtime TestSyscallN/arg-13 (unknown)
=== FAIL: runtime TestCgoPprofThreadNoTraceback (unknown)
=== FAIL: runtime TestVDSO (unknown)
=== FAIL: runtime TestCgoExternalThreadSignal (unknown)
=== FAIL: runtime TestCgoCrashHandler (unknown)
=== FAIL: runtime TestSyscallN/arg-12 (unknown)
=== FAIL: runtime TestSyscallN/arg-7 (unknown)
=== FAIL: runtime TestSyscallN/arg-22 (unknown)
=== FAIL: runtime TestSyscallN/arg-0 (unknown)
=== FAIL: runtime TestSyscallN/arg-16 (unknown)
=== FAIL: runtime TestCgoPprofPIE (unknown)
=== FAIL: runtime TestNetpollDeadlock (unknown)
=== FAIL: runtime TestConcurrentReadsAfterGrowthReflect (unknown)
=== FAIL: runtime TestSyscallN/arg-11 (unknown)
=== FAIL: runtime TestCgoExecSignalMask (unknown)
=== FAIL: runtime TestCgoCheckBytes (unknown)
=== FAIL: runtime TestCgoTracebackContext (unknown)
=== FAIL: runtime TestCgoCallbackGC (unknown)
=== FAIL: runtime TestCgoPanicDeadlock (unknown)
=== FAIL: runtime TestRecoverBeforePanicAfterGoexit2 (unknown)
=== FAIL: runtime TestEnsureDropM (unknown)
=== FAIL: runtime TestBigGOMAXPROCS (unknown)
=== FAIL: runtime TestSyscallN/arg-20 (unknown)
=== FAIL: runtime TestCgoCCodeSIGPROF (unknown)
=== FAIL: runtime TestPanicTraceback (unknown)
=== FAIL: runtime TestCheckPtr (unknown)

Not all are clearly related to cgo, but there are a decent number in there. Potentially related:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Azure build results and reproduce the failures in the windows-amd64 runtime tests, including TestSyscallN and the listed cgo tests. Compare the failures with the related issue #49188; done means identifying the cause and making the affected tests reliable.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.