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

Issue 729864 link

Starred by 1 user

Issue metadata

Status: WontFix
Merged: issue 725516
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

linux_android_rel_ng failing on telemetry_perf_unittests and not retrying

Project Member Reported by pdr@chromium.org, Jun 6 2017

Issue description

The linux_android_rel_ng bot is currently experiencing issues with telemetry_perf_unittests. This is being tracked in  https://crbug.com/725516 

Recent build example:
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/310807

It looks like these tests are failing on the first run and are not retried. I'm not sure a retry would fix this particular case, but I see this failure a lot and I think retrying would reduce flakiness. Should telemetry_perf_unittests be retrying after failing?
 
Mergedinto: 725516
Status: Duplicate (was: Assigned)

Comment 2 by pdr@chromium.org, Jun 6 2017

Status: WontFix (was: Duplicate)
Sorry for the noise, I realized this would be a bad idea after creating the bug.

I had in my head a design like webkit_layout_tests which retry failures and allow the bot to pass if the failures occur without the patch. In this case, we'd be not running patches. There is a retry mechanism where the entire job is retried.
Components: Test>Telemetry
Components: -Speed>Telemetry

Sign in to add a comment