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

Issue 715629 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

autoupdater_unittest erros in M58 UnitTest phase

Project Member Reported by josa...@chromium.org, Apr 26 2017

Issue description

New unittest errors in M58 builders

Log snippet:
autotest-0.0.2-r8003: Running autotest_lib.client.common_lib.cros.autoupdater_unittest
autotest-0.0.2-r8003: testCheckVersion_1 (autotest_lib.client.common_lib.cros.autoupdater_unittest.TestAutoUpdater)
autotest-0.0.2-r8003: Test version check methods work for any build. ... ERROR:root:A trybot paladin or pre-cq build is expected. Version "1111.0.0-rc1" is not a paladin or pre-cq  build.
autotest-0.0.2-r8003: ERROR:root:A trybot paladin or pre-cq build is expected. Version "1111.0.0" is not a paladin or pre-cq  build.
autotest-0.0.2-r8003: ERROR:root:A trybot paladin or pre-cq build is expected. Version "4444.0.0-pgo-generate" is not a paladin or pre-cq  build.
autotest-0.0.2-r8003: ok

Full log:
https://uberchromegw.corp.google.com/i/chromeos_release/builders/asuka-release%20release-R58-9334.B/builds/52/steps/UnitTest/logs/stdio

This is seem on all boards/builders

Nothing obvious in the diffs but there are some Moblab autotest changes but these may be infra related as there are several time outs in the logs 


 
Cc: -haddowk@chromium.org jrbarnette@chromium.org
Owner: haddowk@chromium.org
Status: Available (was: Untriaged)
ok, it seems like the culprit may be autotest change
https://chromium-review.googlesource.com/c/481960/

which is now reverted here https://chromium-review.googlesource.com/c/487722/

I am passing to Keith to evaluate why there are some dependencies here ... 
Owner: jrbarnette@chromium.org
Passing the owner to Richard - I can not explain why my CP of a revert onto a branch broke the autotests in the lab.
Owner: haddowk@chromium.org
I've no idea what happened, and I don't anticipate having
bandwidth to track it down.  But IIUC, the underlying problem
is fixed.

So...  If this is important, someone else will need to do it.
If it's not important, someone else needs to make that final
call, and close with WontFix.

Status: WontFix (was: Available)
Decided there is just not the bandwidth to investigate.

Sign in to add a comment