Issue metadata
Sign in to add a comment
|
Some tests in swaming were wrongly skipped |
||||||||||||||||||||||||
Issue descriptionhttps://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/348342 In this CQ job, chrome_public_test_apk was labelled failed because many tests were wrongly skipped. For those wrongly skipped tests, the status is UNKNOWN, and elapsed_time_ms 0. It would be nice if this doesn't happen. If it's hard to avoid, it's better to rerun this test target than failing it since these are not flaky tests, but some glitches in the infra.
,
Jul 28 2017
I landed a fix for this over yesterday afternoon: https://chromium-review.googlesource.com/c/585866/
,
Jul 28 2017
("over yesterday afternoon" -> "yesterday afternoon")
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tandrii@chromium.org
, Jul 28 2017Components: -Infra>CQ Infra>Client>Chrome