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

Issue 674788 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocking:
issue 661434



Sign in to add a comment

telemetry_unittests failing on chromium.linux/Linux Tests (dbg)(1) and linux_chromium_rel_ng

Project Member Reported by rjkroege@chromium.org, Dec 16 2016

Issue description

telemetry_unittests failing on chromium.linux/Linux Tests (dbg)(1)

Type: build-failure

Builders failed on: 
- Linux Tests (dbg)(1): 
  https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29



 
Owner: oysteine@chromium.org
Status: Assigned (was: Available)
Is this a problem with the catapult roll? oysteine@: can you triage as appropriate?
Blocking: 661434
Cc: oysteine@chromium.org
Owner: nedngu...@google.com
I think http://crrev.com/45cada62 is the culprit; it seems 960s timeout is not enough.

Before this patch it took longer than 30 minutes (on 1 shard).
https://uberchromegw.corp.google.com/i/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/59603

Ned, should we increase the number of shards, or increase timeout?

Comment 3 by thakis@chromium.org, Dec 16 2016

25% of all tryjobs on linux_chromium_rel_ng fail because of this as well atm: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng?numbuilds=200

Comment 4 by thakis@chromium.org, Dec 16 2016

Summary: telemetry_unittests failing on chromium.linux/Linux Tests (dbg)(1) and linux_chromium_rel_ng (was: telemetry_unittests failing on chromium.linux/Linux Tests (dbg)(1))

Comment 5 by thakis@chromium.org, Dec 16 2016

Cc: alexclarke@chromium.org
Could also be https://codereview.chromium.org/2546423002

Since the CQ is currently ~broken because of that, probably best to revert both for now?
Reverting the buildbot recipe. If it doesn't fix the problem, I'll revert the scheduler patch too.

Comment 7 by guidou@chromium.org, Dec 16 2016

Status: Fixed (was: Assigned)
The revert by ksakamoto@ worked. Bot is green now.

Sign in to add a comment