Bugs filed for flaky tests could be much more useful. |
||||
Issue descriptionFor example in the case of https://bugs.chromium.org/p/chromium/issues/detail?id=784890, having the path of the tests abbreviated makes it rather annoying to figure out what the actual test failure is, since the actually important part of the path of the test is missing. Also with the actual path of the test it could look up the owners file and at least file the bug in the appropriate component. Also not sure why it says "multiple builders" but only lists one builder?
,
Dec 14 2017
,
Dec 17
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
,
Dec 18
We appear to do some test name re-writing inside the test step analyzer: https://cs.chromium.org/chromium/infra/go/src/infra/appengine/sheriff-o-matic/som/analyzer/step/test_step.go?l=60 Though it's supposed to leave "http:" or "https:" prefixed test names alone. In the case of https://bugs.chromium.org/p/chromium/issues/detail?id=784890 the prefix was just "http" (no colon). martiniss@: do you remember why testTrunc() has a special case for these?
,
Dec 18
https://cs.chromium.org/chromium/infra/go/src/infra/appengine/sheriff-o-matic/som/analyzer/step/test_step_test.go?q=test_step_test.go&sq=package:chromium&g=0&l=572 is a test case which motivates this I think. Perf tests have full URLs in their names, and IIRC if we don't special case them everything looks super strange. |
||||
►
Sign in to add a comment |
||||
Comment 1 by zhangtiff@chromium.org
, Dec 5 2017