New issue
Advanced search Search tips

Issue 914592 link

Starred by 1 user
Status: Fixed
Owner:
sergeybe...@chromium.org
Closed: Dec 13
Cc:
sergeybe...@chromium.org
jbudorick@chromium.org
chrome-trooper-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocked on:
issue 914604


Sign in to add a comment

Internal failure on Linux FYI Release (AMD R7 240)

Project Member Reported by sunn...@chromium.org, Dec 13 
Last two builds have run for 6 hrs instead of usual 3 hrs and say "Internal failure":

https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28AMD%20R7%20240%29/2469
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28AMD%20R7%20240%29/2468

The failing steps are different (angle_unittests vs tab_capture_end2end_tests), but the stdout for the step looks similar, and there are no swarming logs for the step:

08:06:09.975306 Waiting for results from the following shards: 0
(repeated many times)

Comment 1 by sergeybe...@chromium.org, Dec 13

Owner: sergeybe...@chromium.org
Status: Assigned (was: Available)
Looking at https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20FYI%20Release%20%28AMD%20R7%20240%29/2469 :

The build timed out at 6h - you can see the "execution timeout" set to 6h on the task page under "More Info": https://chromium-swarm.appspot.com/task?id=41bbf2f615741910

The triggered task expired after waiting for 6h: https://chromium-swarm.appspot.com/task?id=41bbf807ad83ea10

It's probably best to set the expiration and total runtime of a triggered task shorter than the runtime of the main build, so the build has a chance to report the failure correctly.

And the reason the task never started is because the only bot that can run it is dead: https://chromium-swarm.appspot.com/bot?id=build115-b1&sort_stats=total%3Adesc

Comment 2 by sergeybe...@chromium.org, Dec 13 

build115-b1 stopped sending metrics on 2018/12/12 02:01:22 PST. I can't SSH to the host - looks like it's hard down. Will call the Labs.

Comment 3 by sergeybe...@chromium.org, Dec 13

Blockedon: 914604

Comment 4 by sergeybe...@chromium.org, Dec 13 

This should be fixed once issue 914604 is resolved.

Comment 5 by sergeybe...@chromium.org, Dec 13

Status: Fixed (was: Assigned)
►

Sign in to add a comment