-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go/internal/modfetch: TestCodeRepo failures due to external repo changes #28856
Comments
Looks like what happened is that github.com/go-yaml/yaml added a new comment to the v2 branch: https://github.com/go-yaml/yaml/commits/v2. (Observe that previous tip was cc @bcmills |
Why are we running tests against repos that are active and not controlled by us? Seems that we should be hitting repos that we control and are pre-baked. |
Adding @rsc since he wrote the original code. |
Related issue #27692. It's another instance of the cmd/go tests relying on an external live repository. |
Change https://golang.org/cl/153460 mentions this issue: |
….2.2 I think we ought to make these tests hermetic, but in the meantime we should at least make them pass. Fixes #27692 Updates #28856 Change-Id: Ia78fa60e998dea3c871f640ffa2ece67b054f866 Reviewed-on: https://go-review.googlesource.com/c/153460 Run-TryBot: Bryan C. Mills <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
@dmitshur, ideally we should make the tests hermetic (for example, by running or emulating a local Git server and substituting paths to point to it). |
Change https://golang.org/cl/168561 mentions this issue: |
Happened again, I sent the patch above to align the expected data for now, waiting for the test to become independent from external repositories. |
New release, it broke again the longtest builder. Align the expected data with the current release. Making these tests independent of external repositories is #28856. This fixes the longtest builder. Updates #28856 Change-Id: I32d2f3325af828d26ab417a5e986e3aeefa1a897 Reviewed-on: https://go-review.googlesource.com/c/go/+/168561 Run-TryBot: Alberto Donizetti <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
Change https://golang.org/cl/198117 mentions this issue: |
Happened again.
From https://build.golang.org/log/b73d1e539a95bac69fec321f90c305f4b69944fe |
Happened again: |
Change https://golang.org/cl/205437 mentions this issue: |
The test for gopkg.in/yaml.v2@v2 assumes that there are no future upstream releases. That assumption empirically does not hold. Backporting fixes to this test is annoying, and other gopkg.in cases are already reasonably covered, so remove the problematic test. Updates #28856 Change-Id: I6455baa1816ac69e02d1ad5d03b82a93e1481a17 Reviewed-on: https://go-review.googlesource.com/c/go/+/205437 Run-TryBot: Bryan C. Mills <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
Change https://golang.org/cl/205439 mentions this issue: |
Change https://golang.org/cl/205438 mentions this issue: |
… test The test for gopkg.in/yaml.v2@v2 assumes that there are no future upstream releases. That assumption empirically does not hold. Backporting fixes to this test is annoying, and other gopkg.in cases are already reasonably covered, so remove the problematic test. Updates #28856 Change-Id: I6455baa1816ac69e02d1ad5d03b82a93e1481a17 Reviewed-on: https://go-review.googlesource.com/c/go/+/205437 Run-TryBot: Bryan C. Mills <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]> (cherry picked from commit f0390ff) Reviewed-on: https://go-review.googlesource.com/c/go/+/205438 Reviewed-by: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
… test The test for gopkg.in/yaml.v2@v2 assumes that there are no future upstream releases. That assumption empirically does not hold. Backporting fixes to this test is annoying, and other gopkg.in cases are already reasonably covered, so remove the problematic test. Updates #28856 Change-Id: I6455baa1816ac69e02d1ad5d03b82a93e1481a17 Reviewed-on: https://go-review.googlesource.com/c/go/+/205437 Run-TryBot: Bryan C. Mills <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]> (cherry picked from commit f0390ff) Reviewed-on: https://go-review.googlesource.com/c/go/+/205439 Reviewed-by: Alexander Rakoczy <[email protected]> TryBot-Result: Gobot Gobot <[email protected]>
This is neither a regression, serious bug, nor an outage, so removing Soon. It should be fixed, but that label is meant for things that are done in the order of days. |
There were some additional cmd/go tests failing on the longtest builder because Specifically (from https://storage.googleapis.com/go-build-log/3c347861/linux-amd64-longtest_bb29e807.log, https://storage.googleapis.com/go-build-log/2229151e/linux-386-longtest_dca9ed82.log, and https://storage.googleapis.com/go-build-log/0fcc0a58/linux-amd64-longtest_642c58db.log):
@bcmills @matloob @jayconrod Is it in scope for this issue to make those tests not fail if rsc.io, or swtch.com, or insecure.go-get-issue-15410.appspot.com are not available (potentially by moving them to vcs-test.golang.org and insecure.vcs-test.golang.org or so), or is it better to make these separate issues? |
@dmitshur, this issue is specifically about |
Sounds good. Factored it out into a standalone issue #40519. |
longtest builders broken again:
|
Change https://golang.org/cl/265819 mentions this issue: |
Updates #28856 Change-Id: I89c564cefd7c5777904bc00c74617dab693373bf Reviewed-on: https://go-review.googlesource.com/c/go/+/265819 Trust: Tobias Klauser <[email protected]> Run-TryBot: Tobias Klauser <[email protected]> Reviewed-by: Alberto Donizetti <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]> TryBot-Result: Go Bot <[email protected]>
Change https://golang.org/cl/265917 mentions this issue: |
…TestCodeRepoVersions Follow-up for CL 265819. Given the -pre tag added recently, a new stable version is likely tagged soon. This would break TestCodeRepoVersions on the longtest builders again. Since the other test cases in codeRepoVersionsTests already provide enough coverage, drop gopkg.in/russross/blackfriday.v2 to avoid breaking TestCodeRepoVersions once the release happens. Updates #28856 Change-Id: If86a637b5e47f59faf9048fc1cbbae6e8f1dcc53 Reviewed-on: https://go-review.googlesource.com/c/go/+/265917 Trust: Tobias Klauser <[email protected]> Run-TryBot: Tobias Klauser <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]> Reviewed-by: Jay Conrod <[email protected]> TryBot-Result: Go Bot <[email protected]>
Change https://golang.org/cl/266178 mentions this issue: |
…oss/blackfriday.v2 from TestCodeRepoVersions Follow-up for CL 265819. Given the -pre tag added recently, a new stable version is likely tagged soon. This would break TestCodeRepoVersions on the longtest builders again. Since the other test cases in codeRepoVersionsTests already provide enough coverage, drop gopkg.in/russross/blackfriday.v2 to avoid breaking TestCodeRepoVersions once the release happens. Updates #28856 Change-Id: If86a637b5e47f59faf9048fc1cbbae6e8f1dcc53 Reviewed-on: https://go-review.googlesource.com/c/go/+/265917 Trust: Tobias Klauser <[email protected]> Run-TryBot: Tobias Klauser <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]> Reviewed-by: Jay Conrod <[email protected]> TryBot-Result: Go Bot <[email protected]> (cherry picked from commit 421d4e7) Reviewed-on: https://go-review.googlesource.com/c/go/+/266178 Trust: Dmitri Shuralyov <[email protected]> Trust: Jay Conrod <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Tobias Klauser <[email protected]>
Change https://golang.org/cl/266302 mentions this issue: |
…oss/blackfriday.v2 from TestCodeRepoVersions Follow-up for CL 265819. Given the -pre tag added recently, a new stable version is likely tagged soon. This would break TestCodeRepoVersions on the longtest builders again. Since the other test cases in codeRepoVersionsTests already provide enough coverage, drop gopkg.in/russross/blackfriday.v2 to avoid breaking TestCodeRepoVersions once the release happens. Updates #28856 Change-Id: If86a637b5e47f59faf9048fc1cbbae6e8f1dcc53 Reviewed-on: https://go-review.googlesource.com/c/go/+/265917 Trust: Tobias Klauser <[email protected]> Run-TryBot: Tobias Klauser <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]> Reviewed-by: Jay Conrod <[email protected]> TryBot-Result: Go Bot <[email protected]> (cherry picked from commit 421d4e7) Reviewed-on: https://go-review.googlesource.com/c/go/+/266178 Trust: Dmitri Shuralyov <[email protected]> Trust: Jay Conrod <[email protected]> Run-TryBot: Dmitri Shuralyov <[email protected]> Reviewed-by: Tobias Klauser <[email protected]> (cherry picked from commit 8687f6d) Reviewed-on: https://go-review.googlesource.com/c/go/+/266302 Trust: Ian Lance Taylor <[email protected]> Run-TryBot: Ian Lance Taylor <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
Seen again at https://build.golang.org/log/f1a0e4f0ab66236cb97d5578af05b873d19af60a
|
The failure in #28856 (comment) doesn't appear to be due to an external code change. Given the |
To reproduce:
Spotted on the longtest builder.
The text was updated successfully, but these errors were encountered: