New issue
Advanced search Search tips

Issue 819273 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

moblab_RunSuite internal failure incorrectly marked as infra failure

Project Member Reported by pprabhu@chromium.org, Mar 6 2018

Issue description

Master CQ build: https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/17924

guado_moblab paladin: https://luci-milo.appspot.com/buildbot/chromeos/guado_moblab-paladin/8812

Failed test: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/181160138-chromeos-test/chromeos2-row1-rack8-host1/

The internal run_suite call took too long so that the whole test was aborted.
This got marked as an infrastructure failure, when it should have been marked as a test failure.
 
Status: Available (was: Untriaged)
More generally, are test timeouts classified as infra failures?

That should probably be fixed, but I don't think it's high priority since it's a non-trivial problem.  Test timeouts can be infra failures and is probably why we handle it this way in the first place.

Sign in to add a comment