New issue
Advanced search Search tips

Issue 858971 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 859031
Owner:
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Android PFQ failure in BuildPackages of chromite

Project Member Reported by kroot@google.com, Jun 29 2018

Issue description

It appears that the Android PFQs are broken due to chromite build failure. Not sure if it's intentionally due to the changes made for:
https://bugs.chromium.org/p/chromium/issues/detail?id=858925

https://uberchromegw.corp.google.com/i/chromeos/builders/caroline-nyc-android-pfq/builds/2501
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_jaq-nyc-android-pfq/builds/2446
https://uberchromegw.corp.google.com/i/chromeos/builders/master-nyc-android-pfq/builds/2519
lure.

chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testBoardWithoutPackage
chromite-0.0.2-r3984: Test that running without a package argument exits with an error. ... FAIL
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowStatusReportOneBoard
chromite-0.0.2-r3984: Test main flow for basic one-board status report. ... Exception during output capturing: AssertionError('expected call to main() to exit cleanly, but it exited with code 1',)
chromite-0.0.2-r3984: FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowStatusReportOneBoardNotSetUp
chromite-0.0.2-r3984: Test main flow for basic one-board status report. ... FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowStatusReportTwoBoards
chromite-0.0.2-r3984: Test main flow for two-board status report. ... Exception during output capturing: AssertionError('expected call to main() to exit cleanly, but it exited with code 1',)
chromite-0.0.2-r3984: FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowUpgradeOneBoard
chromite-0.0.2-r3984: Test main flow for basic one-board upgrade. ... Exception during output capturing: AssertionError('expected call to main() to exit cleanly, but it exited with code 1',)
chromite-0.0.2-r3984: FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowUpgradeTwoBoards
chromite-0.0.2-r3984: Test main flow for two-board upgrade. ... Exception during output capturing: AssertionError('expected call to main() to exit cleanly, but it exited with code 1',)
chromite-0.0.2-r3984: FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testFlowUpgradeTwoBoardsAndHost
chromite-0.0.2-r3984: Test main flow for two-board and host upgrade. ... Exception during output capturing: AssertionError('expected call to main() to exit cleanly, but it exited with code 1',)
chromite-0.0.2-r3984: FAIL
chromite-0.0.2-r3984: ERROR
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testForceWithoutUpgrade
chromite-0.0.2-r3984: Running with --force requires --upgrade or --upgrade-deep. ... ok
chromite-0.0.2-r3984: [chromite.scripts.cros_portage_upgrade_unittest] MainTest.testHelp
chromite-0.0.2-r3984: Test that --help is functioning ... Exception during output capturing: AssertionError('1 != 0',)
chromite-0.0.2-r3984: FAIL
 

Comment 1 by vapier@google.com, Jun 29 2018

Labels: OS-Chrome Pri-1 Type-Bug
Mergedinto: 858925
Status: Duplicate (was: Untriaged)

Comment 2 by vapier@google.com, Jun 29 2018

Status: Started (was: Duplicate)
https://chromium-review.googlesource.com/1120184 is in flight to fix

Comment 3 by vapier@chromium.org, Jun 29 2018

Mergedinto: -858925 859031
Status: Duplicate (was: Started)

Sign in to add a comment