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

Issue 732932 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ sbc@chromium.org
█ kjellander@chromium.org
dchan@chromium.org
harpreet@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Feature

Blocked on:
issue 731900


Sign in to add a comment

Linux ARM should build 'all' target

Project Member Reported by kjellander@chromium.org, Jun 13 2017 
In order to prevent compile regressions, the Linux ARM builds of Chromium should build the 'all' target, not just the following tests, which is the case today:
* nacl_helper_nonsfi_unittests
* nacl_loader_unittests
* sandbox_linux_unittests

This will also help preventing breakages in downstream projects like WebRTC, where Linux ARM is an interesting platform for embedded systems.

Comment 1 by kjellander@chromium.org, Jun 14 2017

Cc: harpreet@chromium.org dchan@chromium.org sbc@chromium.org
Owner: ----
Status: Available (was: Assigned)
I'd like to hear input from the Chrome OS side on that - is it beneficial to have a bot like this in upstream Chromium? Would building 'all' prevent breakages downstream CrOS similar to how it would for WebRTC?

harpreet/dchan: can you answer this or route my question to the right CrOS people?

Background: In https://chromium-review.googlesource.com/c/528078/ the question was raised if the 'Linux ARM' bot is even worth keeping around. I'd like to know if it provides value for CrOS first.

In WebRTC, we've had build errors in the past due to Clang rolls breaking Linux ARM Debug compilation: https://bugs.chromium.org/p/webrtc/issues/detail?id=7090
https://bugs.chromium.org/p/webrtc/issues/detail?id=7024

Comment 2 by sbc@chromium.org, Jun 14 2017 

A followup question:  Does CrOS run any of chrome's unit tests during testing or does it rely on these being run upstream on chromium's tree?
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 15 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment