You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It stops showing new result on the dashboard. And some new builds fail immediately with something like
builder: windows-arm64-11
rev: 998fdce3ae5954735157da43c285022a8bff707f
buildlet: %!s(<nil>)
started: 2023-11-01 22:23:24.823000759 +0000 UTC m=+770933.260919300
ended: 2023-11-01 22:23:31.643393852 +0000 UTC m=+770940.081312402
success: false
Events:
2023-11-01T22:23:24Z get_buildlet
2023-11-01T22:23:31Z finish_get_buildlet after 6.71s; err=500 Internal Server Error; body: remove C:\workdir\go\src\runtime: The process cannot access the file because it is being used by another process.
Build log:
Error: failed to get a buildlet: 500 Internal Server Error; body: remove C:\workdir\go\src\runtime: The process cannot access the file because it is being used by another process.
I'll look into it.
cc @golang/release
The text was updated successfully, but these errors were encountered:
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Nov 2, 2023
The builder seems stuck again, same error message.
I wonder if it has anything to do with #63938 , especially before https://go.dev/cl/538697 . When that test timed out, maybe the process is not completely killed and somehow holds some file open?
All commits in that bad range have failed now, every time cause the undeleteable folder and hang the builder. Manually deleted the folder and restarted the buildlet every time.
Hopefully this time it will work. Optimistically call it fixed.
It stops showing new result on the dashboard. And some new builds fail immediately with something like
I'll look into it.
cc @golang/release
The text was updated successfully, but these errors were encountered: