New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 664304 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

autotest unittest errors

Project Member Reported by nxia@chromium.org, Nov 10 2016

Issue description

autotest test failed in a lot builds in the following two CQ runs. I didn't find any suspicious CLs. Are they just flaky tests? How can we avoid such flakiness? 

dshi@, can you take a quick look and confirm if they're just flakiness?


https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12812

https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/12813


 

Comment 1 by dshi@chromium.org, Nov 10 2016

Cc: jrbarnette@chromium.org
The failed unittest is dut_status_unittest.py
I can't reproduce the error in my local env.

maybe we added some dependancy that doesn't exist on builders. It failed on all builders, don't look like a flake.

+Richard
I've reproduced failures by adding a 2-second sleep to
dut_status._validate_time_range().  The tests were meant
to pass in such a case, so the failures I saw are bugs in
the unit tests.

However, the failures I saw weren't the same set of
failures reported here, so it seems we have other bugs.

I think disabling the tests until we can have more faith
in them is a good choice in this case.

Comment 3 by autumn@chromium.org, Nov 16 2016

Labels: Hotlist-Fixit
Status: Archived (was: Untriaged)
This bug has not been touched in over a year.  It is probably no longer relevant.

Sign in to add a comment