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

Issue 803222 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
chanli@chromium.org
█ robert...@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

No auto-revert if heuristic and try-job have different results?

Project Member Reported by chanli@chromium.org, Jan 17 2018 
This compile try job looks weird: https://ci.chromium.org/p/chromium/builders/luci.chromium.findit/findit_variable/270. Findit has a suspect, but the try job skipped both suspected revision and the revision before it

Comment 1 by st...@chromium.org, Jan 18 2018

Summary: No auto-revert if heuristic and try-job have different results? (was: [Findit] compile try job acting weridly)
For this case https://luci-milo.appspot.com/buildbot/chromium.chromiumos/linux-chromeos-rel/4395, the vr feature was turned on by the auto-reverted culprit (https://chromium-review.googlesource.com/c/chromium/src/+/865955) -- a triggering CL for the compile failure. Without enabling, the obj/chrome/browser/vr/testapp/vr_testapp/vr_test_context.o was not included.

By definition, the recipe does the right thing. It is just an unfortunate timing that the real culprit broke the test  (https://chromium-review.googlesource.com/c/chromium/src/+/868991) landed at the same time.

One possible action for Findit is: if heuristic and try-job have different results, not auto-revert. But instead post two messages to each CL saying two different findings.

Comment 2 by st...@chromium.org, Jan 18 2018

Cc: chanli@chromium.org
Project Member

Comment 3 by sheriffbot@chromium.org, Yesterday (46 hours ago)

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment