-
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
x/telemetry/internal/counter: TestNewFile persistently failing on GOOS=solaris GOARCH=amd64 using Go 1.20 and Go tip #60970
Comments
Change https://go.dev/cl/505580 mentions this issue: |
Updates golang/go#60615 Updates golang/go#60692 Updates golang/go#60965 Updates golang/go#60967 Updates golang/go#60968 Updates golang/go#60970 Updates golang/go#60971 Change-Id: Ifb0320c279e91185ab04c3efa6bf20f2c141dbe1 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/505580 Reviewed-by: Jamal Carvalho <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Hyang-Ah Hana Kim <[email protected]>
Found new dashboard test flakes for:
2023-06-23 12:10 solaris-amd64-oraclerel telemetry@09c2e0cd go@48dbb622 x/telemetry/internal/counter.TestNewFile (log)
2023-06-23 12:10 solaris-amd64-oraclerel telemetry@09c2e0cd go@3adcce5a x/telemetry/internal/counter.TestNewFile (log)
2023-06-23 12:10 solaris-amd64-oraclerel telemetry@09c2e0cd go@6dce882b x/telemetry/internal/counter.TestNewFile (log)
|
Change https://go.dev/cl/508499 mentions this issue: |
TestNewFile is flakay and consistently failing on linux-amd64-wsl. The test checks if the end timestamp in the counter file's metadata is within a reasonable range by computing the time since a test reference timestamp ('now'). Log all involved timestamps for investigation. WSL https://build.golang.org/log/fd86b72f06c8291187d0a30c41d24ddb9e959207 RISCV64 https://build.golang.org/log/3392c1e69a53dd6adf359de10923a771ef77b488 Solaris https://build.golang.org/log/466ee94eb52ce64476d1b75d9a3fc1c26f4a9094 For golang/go#60970 For golang/go#60966 Change-Id: I0a9060cee524761245c7f470938f63c1b6717d1f Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/508499 TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Peter Weinberger <[email protected]> Run-TryBot: Hyang-Ah Hana Kim <[email protected]>
Change https://go.dev/cl/508501 mentions this issue: |
The test checks whether a newly created counter file has the TimeEnd metadata value within expected range, by computing the time difference between the TimeEnd value and a test reference time computed at the beginning of the test. Unfortunately, the reference timestamp calculation used a different time zone than what's used in computing TimeEnd, and caused the test failure on some builders with some probabilities depending on builders' time zones. Here is the log from the test failure that shows this issue. --- FAIL: TestNewFile (0.00s) counter_test.go:177: GOOS linux GOARCH amd64 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 0: days = 7, want 7 < days <= 14 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 13: days = 7, want 7 < days <= 14 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 15: days = 7, want 7 < days <= 14 For golang/go#60970 Fixes golang/go#60966 Change-Id: I52936f5fe12c13f7ccf3c052cbbb9b403fcad332 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/508501 Run-TryBot: Hyang-Ah Hana Kim <[email protected]> Reviewed-by: Peter Weinberger <[email protected]> Run-TryBot: Heschi Kreinick <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
I believe this is done, or obsolete with other work to get telemetry passing on the LUCI builders. |
Updates golang/go#60615 Updates golang/go#60692 Updates golang/go#60965 Updates golang/go#60967 Updates golang/go#60968 Updates golang/go#60970 Updates golang/go#60971 Change-Id: Ifb0320c279e91185ab04c3efa6bf20f2c141dbe1 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/505580 Reviewed-by: Jamal Carvalho <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Hyang-Ah Hana Kim <[email protected]>
TestNewFile is flakay and consistently failing on linux-amd64-wsl. The test checks if the end timestamp in the counter file's metadata is within a reasonable range by computing the time since a test reference timestamp ('now'). Log all involved timestamps for investigation. WSL https://build.golang.org/log/fd86b72f06c8291187d0a30c41d24ddb9e959207 RISCV64 https://build.golang.org/log/3392c1e69a53dd6adf359de10923a771ef77b488 Solaris https://build.golang.org/log/466ee94eb52ce64476d1b75d9a3fc1c26f4a9094 For golang/go#60970 For golang/go#60966 Change-Id: I0a9060cee524761245c7f470938f63c1b6717d1f Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/508499 TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Peter Weinberger <[email protected]> Run-TryBot: Hyang-Ah Hana Kim <[email protected]>
The test checks whether a newly created counter file has the TimeEnd metadata value within expected range, by computing the time difference between the TimeEnd value and a test reference time computed at the beginning of the test. Unfortunately, the reference timestamp calculation used a different time zone than what's used in computing TimeEnd, and caused the test failure on some builders with some probabilities depending on builders' time zones. Here is the log from the test failure that shows this issue. --- FAIL: TestNewFile (0.00s) counter_test.go:177: GOOS linux GOARCH amd64 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 0: days = 7, want 7 < days <= 14 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 13: days = 7, want 7 < days <= 14 counter_test.go:233: now: 2023-07-08 00:00:00 +0000 UTC file: counter.test-go1.19.10-linux-amd64-2023-07-08.v1.count TimeBegin: 2023-07-08 00:00:00 +0800 CST TimeEnd: 2023-07-16 00:00:00 +0800 CST counter_test.go:234: 15: days = 7, want 7 < days <= 14 For golang/go#60970 Fixes golang/go#60966 Change-Id: I52936f5fe12c13f7ccf3c052cbbb9b403fcad332 Reviewed-on: https://go-review.googlesource.com/c/telemetry/+/508501 Run-TryBot: Hyang-Ah Hana Kim <[email protected]> Reviewed-by: Peter Weinberger <[email protected]> Run-TryBot: Heschi Kreinick <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
From https://build.golang.org/log/466ee94eb52ce64476d1b75d9a3fc1c26f4a9094:
This happens on Go 1.20 release branch at Go tip. Very similar to #60966.
CC @golang/solaris, @rorth.
The text was updated successfully, but these errors were encountered: