cyan-chrome-pfq failure due to iwlwifi |
|||
Issue descriptionRecent cyan chrome pfq failing the error pattern attached below. Rajat could you take a look? https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/3108 cl in question: crrev.com/c/1027128 RunCommandError: return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk -- emerge-cyan -p --cols --quiet --root /var/empty -e virtual/target-os [33;01m*[0m Tarballs should not encode ebuild rev numbers (-r#). [33;01m*[0m The ebuild revision field is only for changes to the ebuild itself. [33;01m*[0m If you want to update the source tarball, update the PV instead. [33;01m*[0m bad: foo-0.0.1-r8.tbz2 or foo-0.0.1.tbz2 -> foo-0.0.1-r1.tbz2 [33;01m*[0m good: foo-0.0.8.tbz2 or foo-0.0.1.tbz2 -> foo-0.0.2.tbz2 emerge: there are no ebuilds to satisfy "net-wireless/iwlwifi_rescan" for /var/empty/. (dependency required by "chromeos-base/chromeos-bsp-cyan-0.0.2-r14::cyan" [ebuild]) (dependency required by "virtual/chromeos-bsp-3-r2::cyan-private" [ebuild])
,
May 3 2018
,
May 3 2018
But I do see that the cyan build passed successfully and generated the image for 10643.0.0 (the first build in which this crrev.com/c/1027128 is included). I wonder why on ly PFQ is failing, and if the PFQ needs to be drained or restarted?
,
May 3 2018
Cyan build that includes this CL: https://pantheon.corp.google.com/storage/browser/chromeos-releases/dev-channel/cyan/10643.0.0
,
May 3 2018
Looks like the latest PFQ run was successful: https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/3110 |
|||
►
Sign in to add a comment |
|||
Comment 1 by coconutruben@chromium.org
, May 3 2018