New issue
Advanced search Search tips

Issue 896936 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 896175
Owner: ----
Closed: Oct 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

webkit_layout_tests failed but all shards ended with COMPLETED(SUCCESS)

Project Member Reported by chanli@chromium.org, Oct 18

Issue description

Sample build: https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/75117

There are 93 unexpected failures in webkit_layout_tests step, but all shards end with COMPLETED(SUCCESS)
 
Stdout from a Swarming shard (https://chromium-swarm.appspot.com/task?id=409ac5e14f925d10&refresh=10&show_raw=1) says:

05:30:00.713 5294 Testing completed. Exit status: 2

Not sure why Swarming thinks it's COMPLETED (SUCCESS)
Components: Blink>Infra Infra>Platform>Swarming
Components: -Infra>Platform>Swarming Infra>Platform>Swarming>Admin
It's COMPLETED (SUCCESS) because the script is lying in its stdout, the actual exit code is 0, not 2.

I'm not able to reproduce the bug locally. The exit status of r-w-t is consistent with what the log message says locally.

Looking at the commit history of blinkpy, I can see a few changes quickly reverted after landing recently. Perhaps something was broken? We can trigger some new try jobs on ToT and see if we can see the failure mode.
Mergedinto: 896175
Status: Duplicate (was: Untriaged)

Sign in to add a comment