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

Issue 616168 link

Starred by 1 user
Status: Fixed
Owner:
jbudorick@chromium.org
Closed: Jul 2016
Cc:
█ hzl@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

Silent failures in instrumentation tests

Project Member Reported by jbudorick@chromium.org, May 31 2016 
Some instrumentation test errors, particularly ones involving a crash before the test can log itself as started, are going unnoticed by the test runner. It should be marking them as UNKNOWN.

Comment 1 by jbudorick@chromium.org, May 31 2016

Status: Started (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 1 2016 

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

commit 6f1ecb2db65dc83bc4a445f5a30e0895cf923954
Author: jbudorick <jbudorick@chromium.org>
Date: Wed Jun 01 20:12:53 2016

[Android] Fix UNKNOWN handling for local instrumentation tests.

BUG= 616168 

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

[modify] https://crrev.com/6f1ecb2db65dc83bc4a445f5a30e0895cf923954/build/android/pylib/local/device/local_device_instrumentation_test_run.py

Comment 3 by jbudorick@chromium.org, Jul 12 2016

Status: Fixed (was: Started)
►

Sign in to add a comment