Repeated PaygenTestCanary output from builders |
|||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/quawks-release/builds/1548/steps/PaygenTestCanary/logs/stdio The information is repeated again at the bottom, apparently for the benefit of buildbot. Can we not have buildbot read the normal information and avoid repeating it? 06-30-2017 [07:30:29] Output below this line is for buildbot consumption: @@@STEP_LINK@[Auto-Bug]: autoupdate_EndToEndTest.paygen_au_canary_full: retry_count: 1, ABORT: Autotest client terminated unexpectedly: DUT is pingable, SSHable and did NOT restart un-expectedly. We probably lost connectivity during the test., Host did not return from reboot, 168 reports@https://code.google.com/p/chromium/issues/detail?id=688719@@@ @@@STEP_LINK@[Test-Logs]: autoupdate_EndToEndTest.paygen_au_canary_full: retry_count: 1, ABORT: Autotest client terminated unexpectedly: DUT is pingable, SSHable and did NOT restart un-expectedly. We probably lost connectivity during the test., Host did not return from reboot@http://cautotest/tko/retrieve_logs.cgi?job=/results/126007864-chromeos-test/@@@ @@@STEP_LINK@[Flake-Dashboard]: autoupdate_EndToEndTest.paygen_au_canary_full@https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=autoupdate_EndToEndTest.paygen_au_canary_full@@@ Will return from run_suite with status: ERROR
,
Jun 30 2017
,
Jun 30 2017
What is messy is the duplication of the same information twice. It is already very difficult (for me) to figure out what is actually the root cause of the failure, and most of the things I've looked into have turned out to be infrastructure-related, which makes me regret the time I spent filing bugs and digging into things. Ultimately I'd like the buildbot to have one line at the top: Error: this is the exact thing that went wrong and all you need to know to triage this bug Can we do that?
,
Jul 5 2017
,
Jul 6 2017
,
Jul 6 2017
,
Mar 31 2018
Bulk closing old unconfirmed issues. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jrbarnette@chromium.org
, Jun 30 2017> The information is repeated again at the bottom, apparently for the benefit of buildbot [ ... ] The STEP_LINK lines are there so that there will be links here: https://uberchromegw.corp.google.com/i/chromeos/builders/quawks-release/builds/1548/ The links on that page are (frequently) more interesting than the logs for the build stage. In fact, in this particular case, the stage is reporting actual test failures, so the "PaygenTestCanary/logs/stdio" file isn't interesting, and shouldn't be looked at. The data of interest is the "[Test-Logs]" link: http://cautotest/tko/retrieve_logs.cgi?job=/results/126007864-chromeos-test/ I won't deny that figuring out what matters is non-trivial. Perhaps you could elaborate on what was hard, and why?