Use existing log functionality in test results in sheriff-o-matic |
|||||
Issue descriptionhttps://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/66591 is an example of a build with this feature. The "site_per_process_content_browsertests" test has log data in the test result json. This data is present when viewing the results on the test results server, but sheriff-o-matic doesn't surface this at all to users. It probably should.
,
Sep 18 2017
When you say test results, this is the json test results format that all of recipe land is moving towards correct? json test results format is the format uploaded to the flakiness dashboard correct? Also, when you say "test result json" from this that build link you provided, what link are you referring to under the "site_per_process_content_browsertests" test section? the "swarming.summary" in logdog? Since I have context of this, I am assuming you are referring to the "shard #0 (failed)" swarming log, but I wanted to include it here for context. That being said, an open question in my mind is, what do we actually want sheriff-o-matic to surface to users? just a link to the logs somewhere (what those logs are where they are stored is a conversation happening in crbug.com/765777 )?
,
Sep 18 2017
I'm not sure if all of recipe land is moving towards json test results exactly. It is a fairly standard format, but there's not been a big shift around it? We haven't used it historically, but are moving towards it, but we're a bit of an outlier I guess. But yes, this is the json test results format documented here: https://www.chromium.org/developers/the-json-test-results-format The test result json for that test isn't linked from buildbot I think, unfortunately. You have to kinda manually find that on the flakiness dashboard yourself. The swarming.summary is separate, and not the test results json. I think we want a link on sheriff-o-matic somewhere that just says like "test logs", which links to something with the logs.
,
Oct 10 2017
site_per_process_content_browsertests lists several output files. Just to clarify: None of those is relevant here? And we should construct a link to the test-results dashboard manually using some heuristics with the builder/step names?
,
Dec 15 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
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by eyaich@chromium.org
, Sep 18 2017