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

Issue 662531 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 2
Type: Bug

Blocked on:
issue 661612
issue 662535
issue 662536
issue 662537



Sign in to add a comment

Add upstream builder/tester capacity for Chrome for iOS

Project Member Reported by baxley@chromium.org, Nov 4 2016

Issue description

This is an umbrella bug to link specific things that we will need to add.

Currently the web shell is built and unit tested on the CQ on 64-bit iOS 10, iPad and iPhone simulators. More code will have to be built and tested when Chrome moves there.

Here are examples of some additions we'll need (some may be missing, and these are different priorities):
Build Chrome upstream (~30% increase in build time)
Build with Xcode clang, in addition to Chromium clang. (2X build)
Add chrome unit tests (20% increase runtime)
Test the two latest iOS versions (currently 9 and 10) (2X test)
32-bit and 64-bit testers (2X test)
simulator tests and devices (2+X build and test)
 
Blockedon: 661612 662535
Blockedon: 662536 662537 662538
Components: Infra>Client>iOS Test>iOS
I believe we already run all these tests upstream and have enough capacity. I'll let someone else double-check that, and then we can close the issue.

Comment 5 by baxley@chromium.org, Mar 30 2017

Blockedon: -662538

Comment 6 by baxley@chromium.org, Mar 30 2017

Status: Fixed (was: Available)
Yes, we run things that capture the original intent of the bug. There are more things to add (integration tests on main and CQ, and device tests), but these should be tracked by other bugs.

Sign in to add a comment