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

Issue 732274 link

Starred by 1 user
Status: Fixed
Owner:
█ kjellander@chromium.org
Last visit > 30 days ago
Closed: Aug 2017
Cc:
█ sbc@chromium.org
oprypin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

Add Linux ARM+ARM64 Debug+Release bots

Project Member Reported by kjellander@chromium.org, Jun 12 2017 
Until now, only Linux ARM Release (32-bit) is built and tested. 
Several breakages have happened in Debug or 64-bit configurations ( bug 708104 ).
To be able to spot such breakages more easily, we should setup Debug+Release coverage on ARM 32-bit and 64-bit for the Linux platform.

Test execution on Swarming seems limited to 32-bit ARM due to lack of Linux machines with ARM64 capability in the pool.

Corresponding trybots should also be added. I suggest
* Rename linux_arm -> linux_arm_rel
* New linux_arm_dbg
* New linux_arm64_dbg
* New linux_arm64_rel

It's in WebRTC's interest to have these as it'll give us better protection upstream Chromium (often it's Clang rolls that breaks these configs).

Comment 1 by kjellander@chromium.org, Aug 17 2017

Status: Fixed (was: Assigned)
Most of this work referenced https://bugs.chromium.org/p/webrtc/issues/detail?id=7024 but it has been completed a while back. The bots are called:

linux32_arm_dbg
linux32_arm_rel
linux_arm64_dbg
linux_arm64_rel

since renaming is so painful (if you want to preserve logs).

Notice that there's no coverage upstream Chromium, so if these bots break, it may be hard to troubleshoot.
►

Sign in to add a comment