Skip to content
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

moved GOROOT: unrecognized failures #59933

Closed
gopherbot opened this issue May 2, 2023 · 8 comments
Closed

moved GOROOT: unrecognized failures #59933

gopherbot opened this issue May 2, 2023 · 8 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link

gopherbot commented May 2, 2023

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == "" && date < "2024-01-01"

Issue created automatically to collect these failures.

Example (log):

package fmt is not in GOROOT (/tmp/workdir-host-freebsd-arm64-dmgk/go-moved/src/fmt)
2023/04/25 10:24:16 Failed: exit status 1

FAILED

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 2, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-04-24 13:43 freebsd-arm64-dmgk go@ca9947db (log)
package fmt is not in GOROOT (/tmp/workdir-host-freebsd-arm64-dmgk/go-moved/src/fmt)
2023/04/25 10:24:16 Failed: exit status 1

FAILED
2023-04-24 18:24 freebsd-arm64-dmgk go@c3c53a2c (log)
package fmt is not in GOROOT (/tmp/workdir-host-freebsd-arm64-dmgk/go-moved/src/fmt)
2023/04/25 03:42:00 Failed: exit status 1

FAILED

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-05-02 16:35 aix-ppc64 go@ce7bd333 (log)
package fmt is not in GOROOT (/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go-moved/src/fmt)
2023/05/03 01:16:18 Failed: exit status 1

FAILED

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-11-07 17:04 netbsd-arm64-bsiegert go@46fb7816 (log)
build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined
2023/11/07 17:56:39 Failed: exit status 1

FAILED

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-11-07 17:55 netbsd-arm64-bsiegert go@1d0d4b14 (log)
build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined
2023/11/08 10:24:38 Failed: exit status 1

FAILED

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-11-28 16:59 linux-loong64-3a5000 go@1b59b017 fmt (log)
signal: bus error (core dumped)

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-11-28 16:59 linux-loong64-3a5000 go@1b59b017 fmt (log)
signal: bus error (core dumped)

watchflakes

@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- repo == "go" && section == "moved GOROOT" && test == ""
2023-12-05 18:12 netbsd-arm64-bsiegert go@97c8ff8d (log)
build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined
2023/12/05 19:20:31 Failed: exit status 1

FAILED

watchflakes

@bcmills
Copy link
Contributor

bcmills commented Jan 4, 2024

The failures on this issue look like builder-specific filesystem corruption. Closing and adding a date constraint so that watchflakes will file separate issues for new builder flakes.

@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: Done
Development

No branches or pull requests

2 participants