Issue metadata
Sign in to add a comment
|
mismatched stdio and stdout for PaygenTest |
||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromeos/builders/lars-release/builds/749 The stdio has no errors: https://uberchromegw.corp.google.com/i/chromeos/builders/lars-release/builds/749/steps/PaygenTest/logs/stdio (except a FAIL-ed reset, which seems to have been retried and passed) This is the GS bucket: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/95611192-chromeos-test/hostless/debug autotest.DEBUG has no errors. This is consistent with the AFE which also shows no failures. http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=95611192 We must be missing something.
,
Jan 11 2017
#1 how did you get to that log?
,
Jan 11 2017
I clicked the stdout link for the failed PaygenTest stage. It's a good habit to use the stdout links instead of stdio since after awhile, the stdio links get pruned. But.... and this seems alarming... clicking the stdio link for the failing PaygenTest stage shows me the *canary* stage. What's going on here...
,
Jan 11 2017
Maybe this is a good time to rename the PaygenTest stages to PaygenTestCanary and PaygenTestDev :) :) :)
,
Jan 11 2017
Yep, as I mentioned, dgarrett@'s CL is making its way thru the CQ and that should give us those exact names. :) Still, might want to file a bug for the mismatched stdio and stdout links.
,
Jan 11 2017
Oh I just noticed https://chromium-review.googlesource.com/#/c/425849/ Thanks.
,
Jan 11 2017
Isn't that why I didn't see the error?
,
Jan 11 2017
Yup, most likely if you clicked the stdio (which is indeed what you posted in the OP).
,
Jan 12 2017
I chumped in the rename. I think that fixes this bug as well?
,
Jan 12 2017
Oh... is that why? It just takes the first stage it sees with the name? Idk, I guess we'll have to wait and see if it goes away. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by aaboagye@chromium.org
, Jan 11 2017