exceptions from perf waterfall not showing bot-id |
||||
Issue descriptionProblem with Sheriff-o-Matic I have attached a screenshot of SOM where the infra failures for performance_test_suite are not displayed with the bot-id as the previous infra failures. This is the new perf recipe so I am trying to understand the discrepancy for how this is displayed, the bug may be on the perf side. Can you give me more information on where this is pulled from to understand where the bot id field is missing?
,
Apr 16 2018
It's not obvious from the description what was expected vs what's in that screen shot. Are 'build117-b1', 'build118-b1', 'build120-b1', 'build180-b4' (from the bot affinity alerts) etc the kinds of bot IDs you expected to see in performance_test_suite? Was performance_test_suite recently swarmed or has it always run that way?
,
Apr 16 2018
No this is a new swarming task. Ideally it would have read "bot affinity build65-a7 is broken on chromium.perf...etc" since there are 26 shards on that job so it is ideal to call out the bot id. Above all, I just want to make sure we are plumbing through the right data to SOM. I am trying to understand the discrepancy. We might decide we don't care about bot-id in the title since these are handled automatically now, but I want to make sure we have the right data.
,
May 7 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by eyaich@chromium.org
, Apr 16 2018464 KB
464 KB View Download