New issue
Advanced search Search tips

Issue 674172 link

Starred by 1 user
Status: Started
Owner:
jbudorick@chromium.org
Cc:
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Android test suites flakily timing out on pseudo-lock acquisition

Project Member Reported by jbudorick@chromium.org, Dec 14 2016 
e.g. https://chromium-swarm.appspot.com/task?id=3313709375d21910&refresh=10&show_raw=1

the suite is trying to grab a pseudo-lock before downloading chromium_commands.dex.jar but is unable to do so. There are two problems here:
 1) test suites in chromium shouldn't be downloading anything
 2) test suites that do download things shouldn't hang
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 19 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6e2cfec2af8f4129669c22554ea17d289ba36f2e

commit 6e2cfec2af8f4129669c22554ea17d289ba36f2e
Author: jbudorick <jbudorick@chromium.org>
Date: Mon Dec 19 20:18:16 2016

[Android] Use local build of chromium_commands.dex.jar in chromium tests.

Without this, we were downloading chromium_commands.dex.jar from GCS every
time we tried to use it. This is both unnecessary and potentially problematic,
as catapult/devil's downloading mechanism is currently prone to hanging with
lock failures.

With this change, we will instead use the locally built version of
chromium_commands.dex.jar when available.

BUG=674172

Review-Url: https://codereview.chromium.org/2575003003
Cr-Commit-Position: refs/heads/master@{#439537}

[modify] https://crrev.com/6e2cfec2af8f4129669c22554ea17d289ba36f2e/build/android/devil_chromium.py

Comment 2 by benhenry@google.com, Jan 11 

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.
►

Sign in to add a comment