New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users

Issue metadata

Status: Archived
Last visit > 30 days ago
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

Frequent exceptions on Linux ChromiumOS Tests (dbg)

Project Member Reported by, Jan 27 2017

Issue description

Recently there are a bunch of purples on Linux ChromiumOS Tests (dbg).

Errors are: Either it ran for too long (hard timeout) or it didn't produce I/O for an extended period of time (I/O timeout)

Missing results from the following shard(s): 3

This can happen in following cases:
  * Test failed to start (missing *.dll/*.so dependency for example)
  * Test crashed or hung
  * Task expired because there are not enough bots available and are all used
  * Swarming service experienced problems

Please examine logs to figure out what happened.

By discussing with bpastene@, this might be the issue on browsertests, or we can try increasing the number of shards ran for it on that bot.

Assigned to me first.


Comment 1 by, Jan 27 2017

As I looked at  issue 414808 , 

in the reporter's description: need the ability to specify different sharding value per builder (i.e. debug Windows is ~5x slower than release because of all the extra asserts that catch bugs. so we might want 5 shards for release bots like we have on trybots, but 25 for debug). we'll need this ability for asan trybots as well.

For Linux ChromiumOS Tests (dbg), we may want to increase the number of shards.
Project Member

Comment 2 by, Jan 28 2017

The following revision refers to this bug:

commit a70a7c88a29229fa2fad62b5e1e207baf04d71ec
Author: warx <>
Date: Sat Jan 28 02:17:46 2017

Increase shards level for browser_tests on Linux ChromiumOS Tests (dbg)(1)

Linux ChromiumOS Tests (dbg) is slower than release bots. So try to increase the number of shards here to see if recent timeout exceptions on  could be fixed.

BUG= 686265 

Cr-Commit-Position: refs/heads/master@{#446887}


Comment 3 by, Jan 29 2017

Status: Fixed (was: Assigned)
Since after build #21934 (which this CL is) there are no more exceptions happening, mark it as fixed.

Comment 4 by, Apr 17 2017

Labels: VerifyIn-59

Comment 5 by, May 30 2017

Labels: VerifyIn-60

Comment 6 by, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment