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

Issue 903936 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

kevin64 builders fail to build sci-libs/tensorflow

Project Member Reported by manojgupta@chromium.org, Nov 9

Issue description

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930494883620243008

tensorflow-1.9.0_rc1-r3: 
tensorflow-1.9.0_rc1-r3:  * ERROR: sci-libs/tensorflow-1.9.0_rc1-r3::chromiumos failed (prepare phase):
tensorflow-1.9.0_rc1-r3:  *   Unsupported architecture 'arm64'.
tensorflow-1.9.0_rc1-r3:  * 
tensorflow-1.9.0_rc1-r3:  * Call stack:
tensorflow-1.9.0_rc1-r3:  *     ebuild.sh, line  133:  Called src_prepare
tensorflow-1.9.0_rc1-r3:  *   environment, line 4906:  Called get-tf-cpu-str 'aarch64-cros-linux-gnu'
tensorflow-1.9.0_rc1-r3:  *   environment, line 2533:  Called die
tensorflow-1.9.0_rc1-r3:  * The specific snippet of code:
tensorflow-1.9.0_rc1-r3:  *               die "Unsupported architecture '${arch}'."
tensorflow-1.9.0_rc1-r3:  * 
tensorflow-1.9.0_rc1-r3:  * If you need support, post the output of `emerge --info '=sci-libs/tensorflow-1.9.0_rc1-r3::chromiumos'`,
tensorflow-1.9.0_rc1-r3:  * the complete build log and the output of `emerge -pqv '=sci-libs/tensorflow-1.9.0_rc1-r3::chromiumos'`.
tensorflow-1.9.0_rc1-r3:  * The complete build log is located at '/build/kevin64/tmp/portage/logs/sci-libs:tensorflow-1.9.0_rc1-r3:20181107-200232.log'.
tensorflow-1.9.0_rc1-r3:  * For convenience, a symlink to the build log is located at '/build/kevin64/tmp/portage/sci-libs/tensorflow-1.9.0_rc1-r3/temp/build.log'.
tensorflow-1.9.0_rc1-r3:  * The ebuild environment file is located at '/build/kevin64/tmp/portage/sci-libs/tensorflow-1.9.0_rc1-r3/temp/environment'.
tensorflow-1.9.0_rc1-r3:  * Working directory: '/build/kevin64/tmp/portage/sci-libs/tensorflow-1.9.0_rc1-r3/work/tensorflow-1.9.0-rc1'
tensorflow-1.9.0_rc1-r3:  * S: '/build/kevin64/tmp/portage/sci-libs/tensorflow-1.9.0_rc1-r3/work/tensorflow-1.9.0-rc1'
 
Cc: manojgupta@chromium.org
Labels: cros-arm64
Owner: amoylan@chromium.org
The breakage should be fixed by https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1329990 by disabling ml_service use flag.

Assign now to amoylan@ to make tensorflow build on arm64.
Cc: napper@chromium.org martis@chromium.org amoylan@chromium.org alanlxl@chromium.org claudiomagni@chromium.org
Owner: martis@chromium.org
Status: Assigned (was: Untriaged)
Wow. I didn't know we had an arm64 building.
martis@ will probably be the right owner.
Project Member

Comment 4 by bugdroid1@chromium.org, Nov 20

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/d0112aceb826608df18d601dba9caa4a1cf095c3

commit d0112aceb826608df18d601dba9caa4a1cf095c3
Author: Michael Martis <martis@chromium.org>
Date: Tue Nov 20 22:15:25 2018

sci-libs/tensorflow: support ARM64 userspace.

We had assumed that all ARM boards use 32 bit userspace, but the
new board kevin64 does have 64 bit userspace.

We reuse the standard arm configuration for ARM 64 boards.

BUG= chromium:903936 
TEST=emerge-kevin64 sci-libs/tensorflow

Change-Id: Iafd537192be8c68a92a82c629084e405c2ba5baa
Reviewed-on: https://chromium-review.googlesource.com/1343617
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Michael Martis <martis@chromium.org>
Reviewed-by: Charles . <charleszhao@chromium.org>
Reviewed-by: Michael Martis <martis@chromium.org>

[modify] https://crrev.com/d0112aceb826608df18d601dba9caa4a1cf095c3/sci-libs/tensorflow/tensorflow-1.9.0_rc1.ebuild
[rename] https://crrev.com/d0112aceb826608df18d601dba9caa4a1cf095c3/sci-libs/tensorflow/tensorflow-1.9.0_rc1-r4.ebuild

Status: Fixed (was: Assigned)
This specific issue appears to be fixed now, but we can't reenable ml_service yet due to  crbug.com/906913 .
Project Member

Comment 6 by bugdroid1@chromium.org, Dec 21

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/84cfe11fb1e457eb19f29e0732d046e59ee0fbe2

commit 84cfe11fb1e457eb19f29e0732d046e59ee0fbe2
Author: Andrew Moylan <amoylan@chromium.org>
Date: Fri Dec 21 18:17:24 2018

kevin64: Re-enable USE ml_service

This was disabled because:
- tensorflow didn't have an arm64 build (fixed in crrev.com/c/1343617)
- there was no seccomp policy for arm64 (fixed in crrev.com/c/1377793)

BUG= chromium:903936 
TEST=local kevin64 build
CQ-DEPEND=CL:1377793

Change-Id: Iba423242691e079ab62338c7e93fb0dbc3b7eda4
Reviewed-on: https://chromium-review.googlesource.com/c/1379406
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Andrew Moylan <amoylan@chromium.org>

[modify] https://crrev.com/84cfe11fb1e457eb19f29e0732d046e59ee0fbe2/overlay-kevin64/profiles/base/make.defaults

Sign in to add a comment