New issue
Advanced search Search tips

Issue 707837 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

chromium-try-flakes reports different step is subject and description

Project Member Reported by aga...@chromium.org, Apr 3 2017

Issue description

See https://bugs.chromium.org/p/chromium/issues/detail?id=707313

The bug summary says "gclient sync" is flaky. The bug description says "isolate.archive" is flaky.

Both are true, but it should be filing different bugs for the two different failures.
 
Owner: ----
Status: Available (was: Assigned)
Thanks for reporting this, but unfortunately being quite busy with CQ, Flakiness Dashboard and Flakiness Surface, I probably won't be able to fix this soon.
I think this is a serious bug which should be addressed soon, and probably isn't too hard to address.

At the very least, it seems clear that too few bugs are being filed (since the one I reference should have been two separate bugs, one for each step). Beyond that, the bugs which are filed are confusing.
After looking in more detail, I've noticed that the subject was changed in #1 by timloh@, so the original name was correct. There is no such step as "gclienct sync" in ios-simulator builder.
Status: WontFix (was: Available)
Sorry forgot to address your concern regarding "too few bugs are being filed".

There are two steps that were failing on ios-builder: "update_scripts" and "isolate.archive". There is also "steps" that is purple, but we ignore it since it often replicates an error in another step. Also please note that "isolate.archive" is hidden as a nested step under "isolate".

The bug referenced is for "isolate.archive".

This is the page for the "update_scripts": https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyGQsSBUZsYWtlIg51cGRhdGVfc2NyaXB0cww. Clearly it had many failures recently, but no more than 3 failures a day, which is the minimum required to file a bug.

Sign in to add a comment