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.

Sign up for GitHub

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

Jump to bottom

internal/bytealg: unrecognized failures #61012

Closed
gopherbot opened this issue Jun 26, 2023 · 2 comments
Closed

internal/bytealg: unrecognized failures #61012

gopherbot opened this issue Jun 26, 2023 · 2 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 

#!watchflakes
post <- pkg == "internal/bytealg" && test == ""

Issue created automatically to collect these failures.

Example (log):

vet: open $WORK/b010/vet.cfg: no such file or directory
unicode/utf8: open /tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/go-build2987939947/b023/vet.cfg: no such file or directory

— 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 Jun 26, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "internal/bytealg" && test == ""
2023-06-26 18:04 solaris-amd64-oraclerel tools@d03a819d go@b3ca8d2b internal/bytealg [build] (log) 
vet: open $WORK/b010/vet.cfg: no such file or directory
unicode/utf8: open /tmp/workdir-host-solaris-oracle-amd64-oraclerel/tmp/go-build2987939947/b023/vet.cfg: no such file or directory

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Jun 27, 2023

Duplicate of #46135

@bcmills bcmills marked this as a duplicate of #46135 Jun 27, 2023
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bcmills @gopherbot