microsoft / microsoft/go

Flaky test: TestCgoLookupCNAME, res_nsearch failure

Open
#2,487 0 comments 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

=== RUN   TestCgoLookupCNAME
    cgo_unix_test.go:77: res_nsearch failure
--- FAIL: TestCgoLookupCNAME (30.18s)

darwin-amd64 test [systemcrypto] FIPS

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1577604&view=ms.vss-test-web.build-test-results-tab&runId=43499810&paneView=debug

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 TestCgoLookupCNAME in cgo_unix_test.go around line 77 and inspect the linked darwin-amd64 systemcrypto FIPS build results. Reproduce the res_nsearch failure and determine whether it is specific to that environment or the test. Done means the failure is explained and the flaky test or its environment is addressed with appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.