linux_amd64_longtest flaky: dependency on website(s) for vcs tests
Open
Nobody has claimed this yet.
Flaky
Test
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
This test hit issues accessing https://vcs-test.golang.org:
go: module vcs-test.golang.org/git/prefixtagtests.git/sub: git ls-remote -q origin in $WORK/gopath/pkg/mod/cache/vcs/e451b59ee62e623cdb2396e820b4c1bc9a211927958999ea4f0cc7a47ed1ab04: exit status 128:
fatal: unable to connect to vcs-test.golang.org:
vcs-test.golang.org[0: 35.184.38.56]: errno=Connection timed out
Earlier instance: https://dev.azure.com/dnceng/internal/_build/results?buildId=1401509&view=ms.vss-test-web.build-test-results-tab&runId=40692980&resultId=101972&paneView=debug
Related upstream issues:
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 linux_amd64_longtest and its vcs tests, then review the reported failures involving vcs-test.golang.org and the related upstream issues #40519 and #27494. Done should mean these tests no longer fail because the external website is inaccessible, with the behavior verified in the long test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100