hi, jkardatzke@, do you have any idea why did this happen? Thanks.

Yeah, this is a current known failure due to a bug in the screenshot command. This test shouldn't be blocking the PFQ though...I didn't think it was setup for that yet.

ok, thanks for the info. I will take a further look.

Hmm. It won't block the PFQ, but I think it'll still make life harder for gardeners since they watch these builders to learn about impending test failures introduced in ToT Chrome.

Is  issue 887016  tracking the screenshot issue? It doesn't have an owner -- are you okay with disabling this portion of the test until it's fixed?

Yeah, that's the right issue. I'll go ahead and disable that part of the test today (I need to do another CL which fixes an incorrect test result comment).

ccing this weaks shadow and gardener

I just submitted the last change which should fix this to the Chrome OS CQ now, so this should start passing once that is through. (the required Chrome change has made it through PFQ)

i'm not seeing this on the most recent eve-tot-chrome-pfq-informational run, but ill monitor a build or two more before marking this as fixed.

i saw this fail once yesterday, but not for a while besides that

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8933279491557153616

The one failure yesterday was due to a network issue...it's on our todo list to try to harden that part of the testing.