-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
os: RemoveAll failures with EPERM on OpenBSD #49751
Comments
I looked at the testpoint in question -- it's not using the system "ld" as far as I can tell. Looks more like the test built a small Go program, ran it, and the resulting binary crashed (or did an early exit) without emitting any output. Tried greplogs:
|
It does indeed seem to be specific to
2022-02-07T18:09:07-fa04846/openbsd-386-70 |
Just looking for the
2022-02-07T18:09:07-fa04846/openbsd-386-70 From the variety of failures — and the fact that some are on |
TestMemProfileCheck
failure on OpenBSD
(CC @4a6f656c) |
(attn @golang/openbsd) |
Found new matching dashboard test flakes for:
2022-08-29 18:21 openbsd-386-70 tools@248c34b8 go@3c6a5cdb x/tools/go/packages.TestNewPackagesInOverlay (log)
2022-09-01 03:24 openbsd-amd64-70 tools@49ab44de go@86e9e0ea x/tools/gopls/internal/regtest/watch.TestCreateDependency (log)
|
Found new dashboard test flakes for:
2023-06-16 16:38 openbsd-amd64-72 tools@a4ed05f1 go@606a5a60 x/tools/gopls/internal/regtest/modfile.TestModFileModification (log)
|
Found new dashboard test flakes for:
2023-06-21 11:18 openbsd-386-72 mod@baa5c2d0 go@c4590af1 x/mod/zip.TestCreateFromDir (log)
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Saw a trybot failure in
TestMemProfileCheck
: https://storage.googleapis.com/go-build-log/f46e4835/openbsd-amd64-68_61f03b52.logMaybe not a real issue, and since it seems like the problem is when invoking the system
ld
, I'm inclined to believe this isn't our problem.CC @thanm
The text was updated successfully, but these errors were encountered: