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

Issue 622373 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue webrtc:6081



Sign in to add a comment

linux_chromium_chromeos_ozone_rel_ng hangs linking interactive_ui_tests

Project Member Reported by kjellander@chromium.org, Jun 22 2016

Issue description

Now that I've finally landed and rolled in the ~10 blocking CLs for my https://codereview.chromium.org/2022833002/ I'm stuck at the linux_chromium_chromeos_ozone_rel_ng trybot. It's failing consistently for me (4 attempts) and I don't understand why.

It seems to hang on linking interactive_ui_tests:
[8417/8612] RULE interactive_ui_tests_run:
isolate_66259a49d84685497c67f134062c657d interactive_ui_tests.isolate
command timed out: 2400 seconds without output, attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=3255.023309

I don't have any idea how this can be related to my CL. 
How to proceed?
 
Labels: Proj-Ozone
Owner: phajdan.jr@chromium.org
Status: Assigned (was: Untriaged)
We may need to increase the no-output timeout. I'll try to look into this.

Comment 3 by benhenry@google.com, Jun 27 2016

Status: Started (was: Assigned)
Cc: benhenry@chromium.org
Any update on this? The blocking trybot is stopping the last piece of a very long effort in getting rid of src/third_party/libjingle in Chromium.

benhenry: would it be possible to get anyone from the Ozone team to have a look?
Cc: katrielc@chromium.org
Blocking: webrtc:6081
Cc: d...@chromium.org steve...@chromium.org akes...@chromium.org
Adding some folks who may know more about this bot. Let's try the ozone team next.
Cc: jen...@chromium.org jamescook@chromium.org
cc: current cros gardeners (FYI)

Comment 9 by d...@chromium.org, Jul 6 2016

Cc: phajdan.jr@chromium.org
I don't think this is a CrOS or Ozone issue specifically. It's building a Chrome-for-Linux w/ CrOS flags enabled build, but failing rule is part of the standard Chromium build.

I sampled a few other *_rel_ng bots and didn't see a similar line like:
RULE interactive_ui_tests_run

Maybe this specific builder is configured to build/test differently than the others? +phajdan.jr@, any idea what is factoring into this decision?

Looking at other builds for this builder (https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng), it doesn't seem like they are purple, which suggests that this is a problem with your patch.
Project Member

Comment 10 by bugdroid1@chromium.org, Jul 7 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build.git/+/c3e4c75d8ee898904edeceb683625d5ac2d13d8e

commit c3e4c75d8ee898904edeceb683625d5ac2d13d8e
Author: phajdan.jr <phajdan.jr@chromium.org>
Date: Thu Jul 07 13:54:03 2016

tryserver.chromium.linux: disable time-without-output timeout when build timeout is used

BUG= 622373 

Review-Url: https://codereview.chromium.org/2128843002

[modify] https://crrev.com/c3e4c75d8ee898904edeceb683625d5ac2d13d8e/masters/master.tryserver.chromium.linux/master.cfg

Status: Fixed (was: Started)
I had a successful run with the problematic CL so this seems to have helped - thanks for helping out Pawel, as this CL is critical for WebRTC.
Labels: VerifyIn-54
Status: Verified (was: Fixed)
bulk verified

Sign in to add a comment