New issue
Advanced search Search tips

Issue 917063 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: ----



Sign in to add a comment

where does the test failure come from?

Project Member Reported by xixuan@chromium.org, Dec 20

Issue description

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

SkylabHWTest [bvt-tast-cq] is green and successfully passed:
https://chromeos-swarming.appspot.com/task?id=41e3f74f7b6c0f10&refresh=10

But in stdout, there's a test failure reported at the very end:
https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8926634428890753456/+/steps/SkylabHWTest__bvt-tast-cq___astronaut_/0/stdout

and goldeneye also shows [bvt-tast-cq] as a failure stage:
https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=coral-paladin&buildBranch=master


This only happens when there's already a failed stage "FAILURE SkylabHWTest [bvt-inline] [astronaut]" before. In other green builds like  https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8926609861476228800, [bvt-tast-cq] is green and no failure is reported.


I'm confused... Assign to CI bobby for more clues.


 

Sign in to add a comment