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

Issue 640621 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 626456

Blocking:
issue 792173



Sign in to add a comment

Add cronet_unittests to the bots

Project Member Reported by rohitrao@chromium.org, Aug 24 2016

Issue description

A recent CL contained a compile error in cronet_unittests that was only found by internal ios and android bots.  The cronet component itself is public, but it looks like the public bots neither compile nor run cronet_unittests.

I'm assuming that this was unintentional.  Is there any reason why we shouldn't add this test suite to the public bots?
 
Components: -Internals>Network Internals>Network>Library

Comment 2 by mge...@chromium.org, Aug 24 2016

Labels: -OS-Android
We do have public bots running cronet_unittests on Android.
Cc: mge...@chromium.org
@mgersh could you point me to the bots?  I couldn't find one that ran cronet_unittests when I looked under the "android" column.

If this is covered by bots, why didn't the CQ catch this?  Should that be fixed?
Cc: agrieve@chromium.org hanxi@chromium.org

Comment 6 by mge...@chromium.org, Aug 24 2016

If you're talking about https://codereview.chromium.org/1898873006, that one did cause a failure on our asan builder ( issue 640635 ). Looks like all the failing bots use clang, and the passing ones use gcc (default for android).
Thanks for the pointers!  It sounds like we've got decent coverage on the Android side.

For iOS, I'd like to either add this test suite to the main waterfall or remove it from the internal builders, so that we reduce the possibility of future submarine failures.

@cronet folks, are these tests stable enough to be on the main waterfall?  Would you object if we removed them from the internal builders instead?

Comment 8 by mef@chromium.org, Aug 24 2016

TBH I was unaware that internal iOS builders run any of those, and I'll be fine with excluding them from internal builders.
Owner: mge...@chromium.org
Status: Assigned (was: Untriaged)
Owner: mef@chromium.org

Comment 11 by mef@chromium.org, Aug 29 2016

Blockedon: 626456
Labels: -Pri-1 Pri-2
Owner: smut@chromium.org
Sana, could you take a look at it? We would like to add extra tests for iOS platform.

Comment 13 by s...@google.com, May 15 2017

Cc: -kapishnikov@chromium.org smut@chromium.org
Owner: kapishnikov@chromium.org
My understanding was that cronet_unittests require different gn_args to build. We have an experimental try bot (not part of the CQ) that runs them:
https://uberchromegw.corp.google.com/i/tryserver.chromium.mac/builders/ios-simulator-cronet

And it sets extra gn_args:
https://chromium.googlesource.com/chromium/src/+/master/ios/build/bots/chromium.mac/ios-simulator-cronet.json

Can you get cronet_unittests compiling without these? Then we could run them on the CQ without having to add additional VM capacity. If so, just add them here and trigger a try job on ios-simulator:
https://chromium.googlesource.com/chromium/src/+/master/ios/build/bots/chromium.mac/ios-simulator.json

If it's green you can send out the CL to add cronet_unittests to all the bots.

Alternately we could set all the extra gn_args on ios-simulator, but I don't know what impact that has on the Chromium build.

Comment 14 by mef@chromium.org, Dec 5 2017

Blocking: 792173
Cc: -juliatut...@chromium.org

Comment 16 by mef@chromium.org, Dec 5 2017

Owner: mef@chromium.org
Status: Started (was: Assigned)
Project Member

Comment 17 by bugdroid1@chromium.org, Dec 6 2017

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

commit 639579130d04f71ab1678e4a5da6e2aa488b7672
Author: Misha Efimov <mef@chromium.org>
Date: Wed Dec 06 07:13:26 2017

[Cronet] Run cronet_unittests on iOS bots.

Bug:  640621 
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I33516d4a22a9f2da017749f1cf9eb8cd04314725
Reviewed-on: https://chromium-review.googlesource.com/809192
Reviewed-by: smut <smut@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Reviewed-by: Miriam Gershenson <mgersh@chromium.org>
Commit-Queue: Andrei Kapishnikov <kapishnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#522034}
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/components/cronet/ios/BUILD.gn
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/components/cronet/stale_host_resolver_unittest.cc
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/components/cronet/tools/cr_cronet.py
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/components/cronet/url_request_context_config_unittest.cc
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/ios/build/bots/chromium.fyi/ios-simulator-cronet.json
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/ios/build/bots/chromium.mac/ios-simulator-cronet.json
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/testing/buildbot/gn_isolate_map.pyl
[modify] https://crrev.com/639579130d04f71ab1678e4a5da6e2aa488b7672/testing/buildbot/manage.py

Comment 18 by mef@chromium.org, Dec 6 2017

Status: Fixed (was: Started)

Sign in to add a comment