New issue
Advanced search Search tips

Issue 653147 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

chrome-proxy-tests bot shows 44 entries in sheriff-o-matic

Project Member Reported by twelling...@chromium.org, Oct 5 2016

Issue description

chrome-proxy-tests is failing on numerous steps. There is one entry for each failing step in sheriff-o-matic. Rather than 44 entries for this single bot, there should be one entry that aggregates all of the failures.

Maybe there should be a threshold for how many entries a bot can produce before they all get rolled into one "bot experiencing issues in # steps" entry.

Bot link:
https://uberchromegw.corp.google.com/i/internal.client.clank/builders/chrome-proxy-tests
 
Status: Available (was: Untriaged)
martiniss: this sounds like it might be a duplicate, based on some conversations we've had. I think you mentioned an idea of using a heuristic threshold (say 50% similarity) for merging step failure sets across multiple bots into a single alert?

> ... for merging step failure sets across multiple bots into a single alert?

This is multiple step failures for a single bot. Merging a step failure across multiple bots would be useful too.
This is a known issue. Ideally, this would be solved. Right now we don't really have a solution for something like this; sometimes it gets caught by the perf devices logic I landed, but a lot of the times, it fails all but one test, which means that the logic misses it. Something is really messed up with the test, and the bot.

In the future, it would be caught by the planned logic for merging test failures where a builder fails most, or all, of the tests it ran.
Labels: Milestone-Clank
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 6 2017

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)

Sign in to add a comment