-
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/gopkg.in_natefinch_lumberjack.v2/latest failing #58445
Comments
I think this might instead be linked to gopkg.in flakiness? |
I believe that https://go.dev/cl/466857 "fixes" this given that it skips this test, but I don't think this is flakiness. This test asserts that
|
Let's remove those test cases. If/when we move the |
@gopherbot, please backport to Go 1.20 and 1.19. These tests are broken due to benign external changes. |
Change https://go.dev/cl/466860 mentions this issue: |
Backport issue(s) opened: #58449 (for 1.19), #58450 (for 1.20). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/466861 mentions this issue: |
Change https://go.dev/cl/466862 mentions this issue: |
Found new dashboard test flakes for:
2023-01-30 17:13 linux-386-longtest go@01a5a83c cmd/go/internal/modfetch.TestCodeRepo (log)
2023-01-30 17:13 linux-amd64-longtest go@01a5a83c cmd/go/internal/modfetch.TestCodeRepo (log)
2023-01-30 17:13 linux-amd64-longtest-race go@01a5a83c cmd/go/internal/modfetch.TestCodeRepo (log)
2023-02-09 18:52 linux-386-longtest go@b7880cf6 cmd/go/internal/modfetch.TestCodeRepo (log)
2023-02-09 18:52 linux-amd64-longtest go@b7880cf6 cmd/go/internal/modfetch.TestCodeRepo (log)
2023-02-09 18:52 linux-amd64-longtest-race go@b7880cf6 cmd/go/internal/modfetch.TestCodeRepo (log)
|
…versions of external modules In general it seems ok to assume that an open-source module that did exist will continue to do so — after all, users of open-source modules already do that all the time. However, we should not assume that those modules do not publish new versions — that's really up to their maintainers to decide. Two existing tests did make that assumption for the module gopkg.in/natefinch/lumberjack.v2. Let's remove those two tests. If we need to replace them at some point, we can replace them with hermetic test-only modules (#54503) or perhaps modules owned by the Go project. Updates #58445. Fixes #58449. Change-Id: Ica8fe587d86fc41f3d8445a4cd2b8820455ae45f Reviewed-on: https://go-review.googlesource.com/c/go/+/466862 Reviewed-by: David Chase <[email protected]> Run-TryBot: Bryan Mills <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
…versions of external modules In general it seems ok to assume that an open-source module that did exist will continue to do so — after all, users of open-source modules already do that all the time. However, we should not assume that those modules do not publish new versions — that's really up to their maintainers to decide. Two existing tests did make that assumption for the module gopkg.in/natefinch/lumberjack.v2. Let's remove those two tests. If we need to replace them at some point, we can replace them with hermetic test-only modules (#54503) or perhaps modules owned by the Go project. Updates #58445. Fixes #58450. Change-Id: Ica8fe587d86fc41f3d8445a4cd2b8820455ae45f Reviewed-on: https://go-review.googlesource.com/c/go/+/466861 TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Bryan Mills <[email protected]> Reviewed-by: David Chase <[email protected]>
…ules In general it seems ok to assume that an open-source module that did exist will continue to do so — after all, users of open-source modules already do that all the time. However, we should not assume that those modules do not publish new versions — that's really up to their maintainers to decide. Two existing tests did make that assumption for the module gopkg.in/natefinch/lumberjack.v2. Let's remove those two tests. If we need to replace them at some point, we can replace them with hermetic test-only modules (golang#54503) or perhaps modules owned by the Go project. Fixes golang#58445. Change-Id: Ica8fe587d86fc41f3d8445a4cd2b8820455ae45f Reviewed-on: https://go-review.googlesource.com/c/go/+/466860 Run-TryBot: Bryan Mills <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Auto-Submit: Bryan Mills <[email protected]> Reviewed-by: David Chase <[email protected]>
…versions of external modules In general it seems ok to assume that an open-source module that did exist will continue to do so — after all, users of open-source modules already do that all the time. However, we should not assume that those modules do not publish new versions — that's really up to their maintainers to decide. Two existing tests did make that assumption for the module gopkg.in/natefinch/lumberjack.v2. Let's remove those two tests. If we need to replace them at some point, we can replace them with hermetic test-only modules (golang#54503) or perhaps modules owned by the Go project. Updates golang#58445. Fixes golang#58450. Change-Id: Ica8fe587d86fc41f3d8445a4cd2b8820455ae45f Reviewed-on: https://go-review.googlesource.com/c/go/+/466861 TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Bryan Mills <[email protected]> Reviewed-by: David Chase <[email protected]>
Found new dashboard test flakes for:
2024-01-09 01:36 gotip-linux-386-longtest go@b7c630dc cmd/go/internal/modfetch.TestCodeRepo/github.com_rsc_quote_buggy/c4d4236f (log)
2024-01-09 01:36 gotip-linux-386-longtest go@b7c630dc cmd/go/internal/modfetch.TestCodeRepo/rsc.io_quote/v1.0.0 (log)
|
Failed on https://go.dev/cl/466858.
https://storage.googleapis.com/go-build-log/a1d4a977/linux-amd64-longtest_5b4a2f7a.log
It sounds like this test depends on lumberjack being an abandoned project? But it just tagged a new version: https://pkg.go.dev/gopkg.in/natefinch/lumberjack.v2?tab=versions
cc @bcmills
The text was updated successfully, but these errors were encountered: