veyron_tiger pre-flight release builds failing 100% in UprevAndroid |
||||
Issue descriptionThe veyron_tiger builders for release branches for M62, 63 and 64 have been failing every run. For M62 and M63 the failures go back months. https://ci.chromium.org/buildbot/chromeos_release/veyron_tiger-android-mnc-pre-flight-branch%20release-R64-10176.B/ https://ci.chromium.org/buildbot/chromeos_release/veyron_tiger-android-mnc-pre-flight-branch%20release-R63-10032.B/ https://ci.chromium.org/buildbot/chromeos_release/veyron_tiger-android-mnc-pre-flight-branch%20release-R62-9901.B/ Issues 772846 and 780738 are open, but the current failures seem different -- with the UprevAndroid stages logging multiple errors: 17:47:52: INFO: RunCommand: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpolpURI' -- emerge-veyron_tiger -p --quiet '=chromeos-base/android-container-4328928-r1' in /b/c/cbuild/repository [1;31m17:47:55: ERROR: return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpolpURI' -- emerge-veyron_tiger -p --quiet '=chromeos-base/android-container-4328928-r1' !!! Problem resolving dependencies for =chromeos-base/android-container-4328928-r1 !!! The ebuild selected to satisfy "=chromeos-base/android-container-4328928-r1" for /build/veyron_tiger/ has unmet requirements. - chromeos-base/android-container-4328928-r1::cheets-private USE="cheets_user direncryption -cheets_aosp_userdebug -cheets_local_img -cheets_userdebug" The following REQUIRED_USE flag constraints are unsatisfied: !direncryption The above constraints are a subset of the following complete expression: exactly-one-of ( cheets_aosp_userdebug cheets_user cheets_userdebug ) arm? ( !cheets_aosp_userdebug !cheets_userdebug ) !direncryption cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpolpURI', '--', u'emerge-veyron_tiger', '-p', '--quiet', '=chromeos-base/android-container-4328928-r1'], cwd=/b/c/cbuild/repository, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpolpURI'}[0m [1;31m17:47:55: ERROR: Cannot emerge-veyron_tiger =chromeos-base/android-container-4328928-r1 Is Android pinned to an older version?[0m [1;31m17:47:55: ERROR: Android is pinned. Unpinning Android and continuing build for Android atom chromeos-base/android-container-4328928-r1. This stage will be marked as failed to prevent an uprev.[0m
,
Dec 18 2017
This builder is deprecated as we don't support M any more, only N, it just had not gotten turned off, we can ignore the errors. https://chromium-review.googlesource.com/#/c/chromiumos/chromite/+/807824/ removes the builder for ToT, we can pick it back to 64 and 63 if it is an annoyance there, it does require a repin and restart of the release waterfall to go into effect after it lands.
,
Dec 18 2017
I'll leave it up to you folks as it's not so much a gardener duty (and I'm not gardener anymore). It's just hard to take the waterfall seriously when there's so much red and some of it should be ignored. I'd recommend at least keeping this issue open until 64 cycles out so future investigators don't dig deeper.
,
Jan 18 2018
,
May 17 2018
,
Jul 13
|
||||
►
Sign in to add a comment |
||||
Comment 1 by michae...@chromium.org
, Dec 14 2017