New issue
Advanced search Search tips

Issue 907516 link

Starred by 2 users
Status: Assigned
Owner:
dtu@chromium.org
Cc:
simonhatch@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 880397
issue 885148
issue 885149
issue 885150
issue 907658
issue 907871
issue 863540
issue 863866
issue 880331
issue 880400
issue 885141
issue 885151
issue 907651
issue 907654



Sign in to add a comment

[Bisect failue] The swarming task failed with state "BOT_DIED".

Project Member Reported by maxlg@chromium.org, Nov 21 
The swarming task failed with state "BOT_DIED".

Example: 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/149698ec140000

All of the runs failed. The most common error (20/20 runs) was:
SwarmingTaskError: The swarming task failed with state "BOT_DIED".

Comment 1 by maxlg@chromium.org, Nov 21

Blocking: 885141

Comment 2 by maxlg@chromium.org, Nov 21

Blocking: 885151

Comment 3 by maxlg@chromium.org, Nov 21

Blocking: 863540

Comment 4 by maxlg@chromium.org, Nov 21

Blocking: 863866

Comment 5 by maxlg@chromium.org, Nov 21

Owner: dtu@chromium.org
dtu, seems like crbug/863995 has been fixed. But why bots still die?

Comment 6 by maxlg@chromium.org, Nov 21

Blockedon: 880397

Comment 7 by maxlg@chromium.org, Nov 21

Blocking: 880397

Comment 8 by maxlg@chromium.org, Nov 21

Blockedon: -880397

Comment 9 by maxlg@chromium.org, Nov 21

Blocking: 880400

Comment 10 by maxlg@chromium.org, Nov 21

Blocking: 885148

Comment 11 by maxlg@chromium.org, Nov 21

Blocking: 885149

Comment 12 by maxlg@chromium.org, Nov 21

Blocking: 885150

Comment 13 by maxlg@chromium.org, Nov 21

Blocking: 907658

Comment 14 by maxlg@chromium.org, Nov 21

Blocking: 907654

Comment 15 by maxlg@chromium.org, Nov 21

Blocking: 907651

Comment 16 by maxlg@chromium.org, Nov 21

Blocking: 880331

Comment 17 by alexilin@chromium.org, Nov 22

Blocking: 907871

Comment 18 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment