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

Issue 775355 link

Starred by 0 users

Issue metadata

Status: Duplicate
Merged: issue 774534
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

autotest: lxc.container_pool.pool_unittest.PoolTests flakes a lot

Project Member Reported by vapier@chromium.org, Oct 17 2017

Issue description

can we disable this test until it stops flaking ?

https://uberchromegw.corp.google.com/i/chromeos/builders/betty-arc64-paladin/builds/704/steps/UnitTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/no_vmtest_pre_cq/builds/146351/steps/UnitTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/no_vmtest_pre_cq/builds/146089/steps/UnitTest/logs/stdio

 testCleanup_timeout (autotest_lib.site_utils.lxc.container_pool.pool_unittest.PoolTests)
 Verifies that timed out containers are still destroyed. ... 2017-10-16 15:28:52,987 [MainThread] Pool.__init__ called.  Size: 5
 2017-10-16 15:28:53,001 [pool_monitor] Start event loop.
 2017-10-16 15:28:53,003 [pool_monitor] qsize:0 shortfall:5 workers:3+5
 2017-10-16 15:28:53,082 [pool_monitor] Pool size: 1/5
 2017-10-16 15:28:53,083 [pool_monitor] Pool size: 2/5
 2017-10-16 15:28:53,083 [pool_monitor] Pool size: 3/5
 2017-10-16 15:28:53,083 [pool_monitor] Pool size: 4/5
 2017-10-16 15:28:53,086 [MainThread] Pool.get called.
 2017-10-16 15:28:53,087 [MainThread] Pool.get called.
 2017-10-16 15:28:53,087 [MainThread] Pool.get called.
 2017-10-16 15:28:53,087 [MainThread] Pool.get called.
 2017-10-16 15:28:53,088 [MainThread] Pool.get called.
 2017-10-16 15:28:53,183 [pool_monitor] qsize:0 shortfall:5 workers:3+4
 2017-10-16 15:28:53,261 [pool_monitor] Pool size: 1/5
 2017-10-16 15:28:53,362 [pool_monitor] qsize:0 shortfall:5 workers:7+1
 2017-10-16 15:28:53,376 [pool_monitor] Error: worker 140588376086272 timed out
 2017-10-16 15:28:53,376 [pool_monitor] Error: worker 140588376086272 timed out
 2017-10-16 15:28:53,376 [pool_monitor] Error: worker 140588376086272 timed out
 2017-10-16 15:28:53,376 [pool_monitor] Error: worker 140588376086272 timed out
 2017-10-16 15:28:53,402 [MainThread] Pool.cleanup called.
 2017-10-16 15:28:53,403 [MainThread] Stop requested.
 2017-10-16 15:28:53,477 [pool_monitor] Exit event loop.
 2017-10-16 15:28:53,477 [MainThread] Stopped.
 2017-10-16 15:28:53,477 [MainThread] Emptying container pool
 2017-10-16 15:28:53,477 [MainThread] Done.  Destroyed 0 containers
 FAIL
 2017-10-16 15:28:53,479 [MainThread] Pool.cleanup called.
 2017-10-16 15:28:53,479 [MainThread] Stop requested.
 2017-10-16 15:28:53,479 [MainThread] Stopped.
 2017-10-16 15:28:53,480 [MainThread] Waiting for workers to terminate...
 2017-10-16 15:28:53,594 [MainThread] Emptying container pool
 2017-10-16 15:28:53,594 [MainThread] Done.  Destroyed 0 containers
 ======================================================================
 FAIL: testCleanup_timeout (autotest_lib.site_utils.lxc.container_pool.pool_unittest.PoolTests)
 Verifies that timed out containers are still destroyed.
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "/build/betty-arc64/tmp/portage/chromeos-base/autotest-0.0.2-r8718/work/autotest-0.0.2/site_utils/lxc/container_pool/pool_unittest.py", line 208, in testCleanup_timeout
     self.factory.create_count)
 AssertionError: 9 != 10
 

Comment 1 by ihf@chromium.org, Oct 17 2017

Mergedinto: 774534
Status: Duplicate (was: Available)

Sign in to add a comment