-
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
time: TestLoadFixed failures #69840
Comments
Found new dashboard test flakes for:
2024-10-10 20:06 gotip-openbsd-ppc64 go@9cc737d4 time.TestLoadFixed (log)
2024-10-10 20:07 gotip-openbsd-ppc64 go@d20a4c24 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 15:18 gotip-openbsd-ppc64 go@e3d372ae time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 15:56 gotip-openbsd-ppc64 go@acd072a0 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 18:46 gotip-openbsd-ppc64 go@205ab8a3 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 22:38 gotip-openbsd-ppc64 go@c6531fae time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 01:48 gotip-openbsd-ppc64 go@38f85967 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 01:48 gotip-openbsd-ppc64 go@4bfc81a7 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 01:48 gotip-openbsd-ppc64 go@07533966 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 21:59 gotip-openbsd-ppc64 go@067c0915 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 21:52 gotip-openbsd-ppc64 go@4510586f time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 21:48 gotip-openbsd-ppc64 go@6a49f81e time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 20:54 gotip-openbsd-ppc64 go@8668d7bb time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 18:45 gotip-openbsd-ppc64 go@2e9ed44d time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-21 18:42 gotip-openbsd-ppc64 go@11a03bbb time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 17:24 gotip-openbsd-ppc64 go@a464ffda time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 18:15 gotip-openbsd-ppc64 go@ad7f736d time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 19:58 gotip-openbsd-ppc64 go@d40ae5ef time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-22 22:20 gotip-openbsd-ppc64 go@bdc6dbbc time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-23 16:06 gotip-openbsd-ppc64 go@0f235399 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-24 17:32 gotip-openbsd-ppc64 go@1846dd5a time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-24 19:18 gotip-openbsd-ppc64 go@c2b580a4 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-24 19:25 gotip-openbsd-ppc64 go@15c55801 time.TestLoadFixed (log)
|
This seems to be a problem specific to the openbsd-ppc64 builder. CC @golang/openbsd |
Found new dashboard test flakes for:
2024-10-25 02:56 gotip-openbsd-ppc64 go@711552e9 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-25 03:22 gotip-openbsd-ppc64 go@4226fc59 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-25 04:52 gotip-openbsd-ppc64 go@2ef8e41f time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-25 12:05 gotip-openbsd-ppc64 go@e5e552b8 time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-30 15:41 gotip-openbsd-ppc64 go@aefb173b time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-30 15:35 gotip-openbsd-ppc64 go@7b3ac0ca time.TestLoadFixed (log)
|
Found new dashboard test flakes for:
2024-10-30 15:31 gotip-openbsd-ppc64 go@d51f92e7 time.TestLoadFixed (log)
|
By reinstalling a machine from scratch with OpenBSD 7.5, I confirm that the sign behavior changed in the October new version. But I don't think you should blame OpenBSD, rather recognize this is a long-standing debate. There is good background at StackOverflow:
Can't we just use a different test string that stays out of the conflicting POSIX and ISO 8601 standards and interpretations? Or is there some critical Go dependence at stake here that I'm overlooking? |
CL 625197 is an implementation of #69840 (comment). |
Change https://go.dev/cl/625197 mentions this issue: |
@n2vi I guess I don't see how it serves OpenBSD to produce a different result from other Unix systems. While I agree that these timezones are confusing and shouldn't be used, I don't see a reason for them to be differ from one system to another. That just increases the confusion. In any case CL 625197 will address the problem. Thanks @dmitshur . |
This stops the test from failing with a known failure mode, and creates time to look into what the next steps should be, if any. For #69840. Change-Id: I060903d256ed65c5dfcd70ae76eb361cab63186f Cq-Include-Trybots: luci.golang.try:gotip-openbsd-amd64 Reviewed-on: https://go-review.googlesource.com/c/go/+/625197 Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Eric Grosse <[email protected]>
Should be fixed now. |
Found new dashboard test flakes for:
2024-11-06 22:48 go1.23-openbsd-ppc64 release-branch.go1.23@c390a1c2 time.TestLoadFixed (log)
|
@gopherbot Please open backport issues. This test failure is due to a change in the tzdata files on OpenBSD. We should either backport the (trivial) fix or have some other way to ignore the test failure on the builders. |
Backport issue(s) opened: #70238 (for 1.22), #70239 (for 1.23). 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/627416 mentions this issue: |
Change https://go.dev/cl/627575 mentions this issue: |
This stops the test from failing with a known failure mode, and creates time to look into what the next steps should be, if any. For #69840. Fixes #70238. Change-Id: I060903d256ed65c5dfcd70ae76eb361cab63186f Reviewed-on: https://go-review.googlesource.com/c/go/+/625197 Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Eric Grosse <[email protected]> (cherry picked from commit bea9b91) Reviewed-on: https://go-review.googlesource.com/c/go/+/627416 Reviewed-by: Dmitri Shuralyov <[email protected]> Commit-Queue: Ian Lance Taylor <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]>
This stops the test from failing with a known failure mode, and creates time to look into what the next steps should be, if any. For #69840 Fixes #70239 Change-Id: I060903d256ed65c5dfcd70ae76eb361cab63186f Reviewed-on: https://go-review.googlesource.com/c/go/+/625197 Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Eric Grosse <[email protected]> (cherry picked from commit bea9b91) Reviewed-on: https://go-review.googlesource.com/c/go/+/627575 Reviewed-by: Dmitri Shuralyov <[email protected]> TryBot-Bypass: Dmitri Shuralyov <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]>
Found new dashboard test flakes for:
2024-11-19 17:52 go1.23-openbsd-ppc64 release-branch.go1.23@3726f07c time.TestLoadFixed (log)
|
Should be fixed on release branches too, now. Closing optimistically. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: