-
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
x/build/cmd/coordinator: some linux-amd64 trybot builds getting stuck at the end #36629
Comments
See also #32032. |
Also got stuck in the same spot in
builder: js-wasm
rev: 2c418b7c37335c344fc90c8f4868bb95577f84f8
buildlet: http://10.240.0.6 GCE VM: buildlet-js-wasm-rn6557f9f
started: 2020-01-24 18:14:34.902956502 +0000 UTC m=+871893.128356397
status: still running
Events: Build log: Testing packages.ok archive/tar 4.143s os/user with tag osusergook os/user 1.087s Testing without libgcc.ok net 1.239s [no tests to run] ../test/bench/go1../test |
Edit: The trybot did end up passing. At https://farmer.golang.org/try?commit=1ac5913e, I'm seeing what seems to be a similar issue with the linux-amd64-unified trybot. It's stuck on testsanitizers instead though. Details
|
I've observed a few more instances of this with I've filed #52998 for the problem with With the above, I don't think there's anything left to do in this issue, given we understand what happened and have tracking issues for problems still happening today, so closing. |
There are two trybot invocations that were started on January 6th, 2020:
They still haven't finished. They look like this:
All builds other than linux-amd64 passed. linux-amd64 gets to the end and then doesn't complete. Its log is:
Note the many repeated "still_waiting_on_test test:7_10" events at the end.
/cc @toothrot @cagedmantis
The text was updated successfully, but these errors were encountered: