New issue
Advanced search Search tips

Issue 717316 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

Flaky chromite timeout unittest

Project Member Reported by ayatane@chromium.org, May 1 2017

Issue description

Example build: https://luci-milo.appspot.com/buildbot/chromeos/veyron_mighty-paladin/5161

Unittest stage output: https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fveyron_mighty-paladin%2F5161%2F%2B%2Frecipes%2Fsteps%2FUnitTest%2F0%2Fstdout

chromite-0.0.2-r2955: ======================================================================
chromite-0.0.2-r2955: FAIL: [chromite.lib.timeout_util_unittest] TestWaitFors.testWaitForSuccess1
chromite-0.0.2-r2955: Test success after a few tries.
chromite-0.0.2-r2955: ----------------------------------------------------------------------
chromite-0.0.2-r2955: Traceback (most recent call last):
chromite-0.0.2-r2955:   File "/mnt/host/source/chromite/lib/timeout_util.py", line 171, in TimeoutWrapper
chromite-0.0.2-r2955:     return func(*args, **kwargs)
chromite-0.0.2-r2955:   File "/mnt/host/source/chromite/lib/timeout_util_unittest.py", line 136, in testWaitForSuccess1
chromite-0.0.2-r2955:     self.assertEquals(4, self.GetTrySeconds())
chromite-0.0.2-r2955: AssertionError: 4 != 7
chromite-0.0.2-r2955: 
chromite-0.0.2-r2955: ----------------------------------------------------------------------
chromite-0.0.2-r2955: Ran 14 tests in 27.913s
chromite-0.0.2-r2955: 
chromite-0.0.2-r2955: FAILED (failures=1)
c
 
Owner: dgarr...@chromium.org
This is almost certainly tied to CPU load when the test is running.
Status: Archived (was: Untriaged)

Sign in to add a comment