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

Issue 834379 link

Starred by 1 user
Status: Verified
Owner:
manojgupta@chromium.org
Closed: Apr 2018
Cc:
█ laszio@chromium.org
cmt...@chromium.org
saintlou@google.com
josa...@google.com
puneetster@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug
Build-Toolchain



Sign in to add a comment

dev-lang/rust-1.25.0 fails to build in chromiumos-sdk

Project Member Reported by rahulchaudhry@chromium.org, Apr 18 2018 
emerge of dev-lang/rust-1.25.0 is failing in chromiumos-sdk with:
!!! Couldn't download 'rust-std-1.24.0-x86_64-unknown-linux-gnu.tar.gz'. Aborting.

Looking at the rust ebuild, it downloads previous version of 'std' as STAGE0.
i.e. emerge rust-1.25.0 tries to download rust-std-1.24.0, and fails to fetch it from the mirrors.

This is resulting in chromiumos-sdk builds to fail: https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8708

The first failed build started at Tue Apr 17 21:31.
I suspect https://chromium-review.googlesource.com/1013206: dev-lang/rust: upgrade to rust 1.25
which was pushed a few hours before that.

Comment 1 by cmt...@chromium.org, Apr 18 2018

Cc: cmt...@chromium.org

Comment 2 by manojgupta@chromium.org, Apr 19 2018 

cargo is faling to build now :(

https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8710

cargo-0.21.0: error: unnecessary `unsafe` block
cargo-0.21.0:   --> src/cargo/util/lazy_cell.rs:51:9
cargo-0.21.0:    |
cargo-0.21.0: 51 |         unsafe {
cargo-0.21.0:    |         ^^^^^^ unnecessary `unsafe` block
cargo-0.21.0:    |
cargo-0.21.0: note: lint level defined here
cargo-0.21.0:   --> src/cargo/lib.rs:1:9
cargo-0.21.0:    |
cargo-0.21.0: 1  | #![deny(unused)]
cargo-0.21.0:    |         ^^^^^^
cargo-0.21.0:    = note: #[deny(unused_unsafe)] implied by #[deny(unused)]
cargo-0.21.0: 
cargo-0.21.0: error: aborting due to previous error
cargo-0.21.0: 
cargo-0.21.0: error: Could not compile `cargo`.
cargo-0.21.0: 
cargo-0.21.0: To learn more, run the command again with --verbose.

Comment 5 by cmt...@chromium.org, Apr 19 2018

Labels: -Pri-1 Pri-0
This is causing all of the toolchain builders (main waterfall, rotating, etc) that build with llvm-next to fail in the SetupBoard stage.  It needs to be fixed ASAP!

Pending 1/3, Building 0/0, Retrying 1, [Time 10:03:25 | Elapsed 17m14.1s | Load 14.68 23.63 18.92]
Retrying emerge of dev-lang/rust-1.25.0.
Started dev-lang/rust-1.25.0 (logged in /tmp/rust-1.25.0-Ttlcl4)
=== Start output for job rust-1.25.0 (0m2.1s) ===
rust-1.25.0: >>> Emerging (1 of 1) dev-lang/rust-1.25.0::chromiumos
rust-1.25.0:  * rustc-1.25.0-src.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...          [ ok ]
rust-1.25.0:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
rust-1.25.0:                                  Dload  Upload   Total   Spent    Left  Speed
rust-1.25.0: 
rust-1.25.0:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
rust-1.25.0:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
rust-1.25.0: curl: (22) The requested URL returned error: 404 Not Found
rust-1.25.0:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
rust-1.25.0:                                  Dload  Upload   Total   Spent    Left  Speed
rust-1.25.0: 
rust-1.25.0:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
rust-1.25.0:   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
rust-1.25.0: curl: (22) The requested URL returned error: 404 Not Found
rust-1.25.0: !!! Couldn't download 'rust-std-1.24.0-x86_64-unknown-linux-gnu.tar.gz'. Aborting.
rust-1.25.0:  * Fetch failed for 'dev-lang/rust-1.25.0', Log file:
rust-1.25.0:  *  '/var/log/portage/dev-lang:rust-1.25.0:20180418-170326.log'
rust-1.25.0: >>> Failed to emerge dev-lang/rust-1.25.0, Log file:
rust-1.25.0: >>>  '/var/log/portage/dev-lang:rust-1.25.0:20180418-170326.log'
rust-1.25.0: 
rust-1.25.0:  * Messages for package dev-lang/rust-1.25.0:
rust-1.25.0: 
rust-1.25.0:  * Fetch failed for 'dev-lang/rust-1.25.0', Log file:
rust-1.25.0:  *  '/var/log/portage/dev-lang:rust-1.25.0:20180418-170326.log'
=== Complete: job rust-1.25.0 (0m2.1s) ===
Failed dev-lang/rust-1.25.0 (in 0m2.1s). Your build has failed.
Pending 1/3, [Time 10:03:28 | Elapsed 17m16.2s | Load 13.51 23.24 18.81]
Packages failed:
	dev-lang/rust-1.25.0
ERROR   : Wed Apr 18 10:03:28 PDT 2018
ERROR   :  PGID  PPID   PID     ELAPSED     TIME %CPU COMMAND
ERROR   : Arguments of 10: ./update_chroot '--nousepkg' '--toolchain_boards' 'samus'
ERROR   : Backtrace:  (most recent call is last)
ERROR   :  update_chroot:129:main(), called: die_err_trap  
ERROR   : 
ERROR   : Command failed:
ERROR   :   Command 'sudo -E ${EMERGE_CMD} "${EMERGE_FLAGS[@]}" virtual/target-sdk world' exited with nonzero code: 1
10:03:29: ERROR: 
return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpsFmVmt' 'USE=-cros-debug -tests_cheets_SELinuxTest -tests_network_VPNConnect.l2tpipsec_psk -tests_network_VPNConnect.l2tpipsec_xauth -tests_platform_SyncCrash -tests_power_DarkResumeDisplay -tests_power_DarkResumeShutdownServer -tests_security_OpenFDs -tests_security_SMMLocked chrome_internal llvm-next thinlto' 'FEATURES=separatedebug -separatedebug splitdebug' 'CHROME_ORIGIN=LOCAL_SOURCE' -- ./update_chroot --nousepkg --toolchain_boards samus
cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpsFmVmt', u'USE=-cros-debug -tests_cheets_SELinuxTest -tests_network_VPN

Comment 6 by manojgupta@chromium.org, Apr 19 2018

Owner: manojgupta@chromium.org
It should get fixed after current SDK builder run finishes.

Comment 7 by laszio@chromium.org, Apr 19 2018

Cc: laszio@chromium.org

Comment 8 by manojgupta@chromium.org, Apr 20 2018

Status: Verified (was: Assigned)

Comment 9 by hychao@chromium.org, Apr 20 2018

Status: Started (was: Verified)
still seeing setup board failure, different reason

https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Famd64-llvm-next-toolchain%2F612%2F%2B%2Frecipes%2Fsteps%2FSetupBoard%2F0%2Fstdout

rust-1.25.0: 
rust-1.25.0: couldn't find required command: "armv7a-cros-linux-gnueabi-clang"
rust-1.25.0: 
rust-1.25.0: ', bootstrap/sanity.rs:66:13
rust-1.25.0: note: Run with `RUST_BACKTRACE=1` for a backtrace.
rust-1.25.0: failed to run: /var/tmp/portage/dev-lang/rust-1.25.0/work/rustc-1.25.0-src/build/bootstrap/debug/bootstrap build --config cros-config.toml
rust-1.25.0: Build completed unsuccessfully in 0:00:39
rust-1.25.0:  * ERROR: dev-lang/rust-1.25.0::chromiumos failed (compile phase):
rust-1.25.0:  *   (no error message)
rust-1.25.0:  * 
rust-1.25.0:  * Call stack:
rust-1.25.0:  *     ebuild.sh, line 133:  Called src_compile
rust-1.25.0:  *   environment, line 3534:  Called die
rust-1.25.0:  * The specific snippet of code:
rust-1.25.0:  *       ${EPYTHON} x.py build --config cros-config.toml || die
rust-1.25.0:  * 
rust-1.25.0:  * If you need support, post the output of `emerge --info '=dev-lang/rust-1.25.0::chromiumos'`,
rust-1.25.0:  * the complete build log and the output of `emerge -pqv '=dev-lang/rust-1.25.0::chromiumos'`.
rust-1.25.0:  * The complete build log is located at '/var/log/portage/dev-lang:rust-1.25.0:20180419-170342.log'.
rust-1.25.0:  * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-lang/rust-1.25.0/temp/build.log'.
rust-1.25.0:  * The ebuild environment file is located at '/var/tmp/portage/dev-lang/rust-1.25.0/temp/environment'.
rust-1.25.0:  * Working directory: '/var/tmp/portage/dev-lang/rust-1.25.0/work/rustc-1.25.0-src'
rust-1.25.0:  * S: '/var/tmp/portage/dev-lang/rust-1.25.0/work/rustc-1.25.0-src'
rust-1.25.0: >>> Failed to emerge dev-lang/rust-1.25.0, Log file:

Comment 10 by manojgupta@chromium.org, Apr 20 2018

Status: Verified (was: Started)
The build being referred in #9 had started before SDK builder finished.
Project Member

Comment 11 by bugdroid1@chromium.org, Apr 20 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/8b2b38b482ee036d08967c4a6a4029cd07e10fc9

commit 8b2b38b482ee036d08967c4a6a4029cd07e10fc9
Author: Manoj Gupta <manojgupta@google.com>
Date: Fri Apr 20 09:48:44 2018

cbuildbot: SDK Test - copy all host packages to new pkgdir.

Currently only a subset of packages is copied. As a result,
using --usepkgonly fails for non-cross packages.

e.g. An older rust version was installed in SDKTest stage
https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8712

BUG= chromium:834379 
TEST=chromiumos-sdk tryjob passed.
TEST=https://ci.chromium.org/p/chromeos/builds/b8948795294190790288

Change-Id: Ifcccaacb33da5536ea72957e4f487c27b3fee03a
Reviewed-on: https://chromium-review.googlesource.com/1020783
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/8b2b38b482ee036d08967c4a6a4029cd07e10fc9/cbuildbot/stages/sdk_stages.py
Project Member

Comment 12 by bugdroid1@chromium.org, Apr 20 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f40055b535dceae2b9cbe3ce2f8b4b60d24713c0

commit f40055b535dceae2b9cbe3ce2f8b4b60d24713c0
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri Apr 20 12:53:09 2018

Roll src/third_party/chromite/ a46a52500..8b2b38b48 (1 commit)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/a46a525000ae..8b2b38b482ee

$ git log a46a52500..8b2b38b48 --date=short --no-merges --format='%ad %ae %s'
2018-04-19 manojgupta cbuildbot: SDK Test - copy all host packages to new pkgdir.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:834379 


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I4edc49502d212314e5839d8197112b9f673931b0
Reviewed-on: https://chromium-review.googlesource.com/1021184
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#552311}
[modify] https://crrev.com/f40055b535dceae2b9cbe3ce2f8b4b60d24713c0/DEPS
►

Sign in to add a comment