Home | Search
Login

Builder Android Cronet ARM64 Builder Build #90373

Results:

build successful

Trigger Info:

Execution:

Steps and Logfiles:

Show:
  1. ( 12 mins 27 secs ) steps
    running steps via annotated script
  2. ( 10 secs ) update_scripts
    update_scripts
  3. ( 3 ms ) setup_properties
    setup_properties
  4. ( 3 ms ) LUCI Migration
    LUCI Migration
  5. ( 4 ms ) LogDog Bootstrap
    LogDog Bootstrap
  6. ( 5 ms ) setup_build
    setup_build
    running recipe: "cronet"
  7. ( 6 secs ) remove .cipd
    remove .cipd
  8. ( 1 mins 56 secs ) cleanup index.lock
    cleanup index.lock
  9. ( 2 mins 35 secs ) bot_update
    bot_update
    [61GB/492GB used (12%)]
  10. ( 4 ms ) clean local files
    clean local files
  11. ( 3 ms ) ensure_goma
    ensure_goma
  12. ( 4 ms ) ensure_goma.ensure_installed
    ensure_goma.ensure_installed
  13. ( 7 secs ) clobber
    clobber
  14. ( 24 secs ) gclient runhooks
    gclient runhooks
  15. ( 40 secs ) generate_build_files
    generate_build_files
  16. ( 1 ms ) preprocess_for_goma
    preprocess_for_goma
  17. ( 1 ms ) preprocess_for_goma.goma cache directory
    preprocess_for_goma.goma cache directory
  18. ( 1 ms ) preprocess_for_goma.start_goma
    preprocess_for_goma.start_goma
  19. ( 1 ms ) preprocess_for_goma.start cloudtail
    preprocess_for_goma.start cloudtail
  20. ( 6 mins ) compile
    compile
  21. ( 1 ms ) compile confirm no-op
    compile confirm no-op
  22. ( 3 ms ) postprocess_for_goma
    postprocess_for_goma
  23. ( 1 ms ) postprocess_for_goma.goma_jsonstatus
    postprocess_for_goma.goma_jsonstatus
  24. ( 1 ms ) postprocess_for_goma.goma_stat
    postprocess_for_goma.goma_stat
  25. ( 1 ms ) postprocess_for_goma.stop_goma
    postprocess_for_goma.stop_goma
  26. ( 8 secs ) postprocess_for_goma.upload_log
    postprocess_for_goma.upload_log
  27. ( 3 ms ) postprocess_for_goma.stop cloudtail
    postprocess_for_goma.stop cloudtail
  28. ( 4 ms ) sizes
    sizes
    sizes
    <div class="BuildResultInfo">
    </div>
  29. ( 4 ms ) resource_sizes (CronetSample.apk)
    resource_sizes (CronetSample.apk)
    resource_sizes (CronetSample.apk)
    <div class="BuildResultInfo">
    </div>
  30. ( 4 ms ) recipe result
    recipe result

Build Properties:

NameValueSource
$recipe_engine/runtime {"is_experimental":false,"is_luci":false} Annotation(LUCI Migration)
luci_migration {"status":"ok"} Annotation(LUCI Migration)
log_location "logdog://logs.chromium.org/chromium/bb/chromium.android/Android_Cronet_ARM64_Builder/90373/+/recipes/annotations" Annotation(LogDog Bootstrap)
logdog_prefix "bb/chromium.android/Android_Cronet_ARM64_Builder/90373" Annotation(LogDog Bootstrap)
logdog_project "chromium" Annotation(LogDog Bootstrap)
got_angle_revision "5598148b761380773c4e650b5b67f47553b0f090" Annotation(bot_update)
got_buildtools_revision "0dd5c6f980d22be96b728155249df2da355989d9" Annotation(bot_update)
got_nacl_revision "e6ce828ef60c4c1438867b535efbbb5d9a177c0e" Annotation(bot_update)
got_src_revision "9b866113743ca04361daf9e63c30ae190ca60da4" Annotation(bot_update)
got_src_revision_cp "refs/heads/master@{#574722}" Annotation(bot_update)
got_swarming_client_revision "9a518d097dca20b7b00ce3bdfc5d418ccc79893a" Annotation(bot_update)
got_v8_revision "6234bd459ccde6d2aa3481ec65d055619f3fb75b" Annotation(bot_update)
got_v8_revision_cp "refs/heads/6.9.353@{#1}" Annotation(bot_update)
got_webrtc_revision "895617fa9bc36c240b37d47402cdb341ecadf994" Annotation(bot_update)
got_webrtc_revision_cp "refs/heads/master@{#23955}" Annotation(bot_update)
recipe "cronet" Annotation(setup_properties)
blamelist ["fdoray@chromium.org","hcarmona@chromium.org","hgrandinetti@chromium.org","iclelland@chromium.org","liberato@chromium.org","v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com","zqzhang@google.com"] Build
branch "master" Build
buildnumber 90373 Build
project "src" Build
repository "https://chromium.googlesource.com/chromium/src" Build
requestedAt 1531429595 Build
revision "9b866113743ca04361daf9e63c30ae190ca60da4" Build
slavename "slave188-c1" BuildSlave
buildername "Android Cronet ARM64 Builder" Builder
git_revision "9b866113743ca04361daf9e63c30ae190ca60da4" Change
scheduler "chromium_commits" Scheduler
buildbotURL "https://build.chromium.org/p/chromium.android/" master.cfg
mastername "chromium.android" master.cfg
workdir "/b/build/slave/Android_Cronet_ARM64_Builder" slave

Blamelist:

  1. (iclellandohnoyoudont@chromium.org)
  2. (hgrandinettiohnoyoudont@chromium.org)
  3. (liberatoohnoyoudont@chromium.org)
  4. (hcarmonaohnoyoudont@chromium.org)
  5. (v8-ci-autoroll-builderohnoyoudont@chops-service-accounts.iam.gserviceaccount.com)
  6. (fdorayohnoyoudont@chromium.org)
  7. (hgrandinettiohnoyoudont@chromium.org)
  8. (zqzhangohnoyoudont@google.com)

Timing:

Create N/A
Start Thursday, 12-Jul-18 21:18:08 UTC
End Thursday, 12-Jul-18 21:30:36 UTC
Pending N/A
Execution 12 mins 27 secs

All Changes:

  1. Use standard uppercase names for OT test methods

    Changed by iclellandohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:04:09 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 67f3705fc7dc9cec4a8059936441b436f4a20a39

    Comments

    Use standard uppercase names for OT test methods
    
    This change brings the OriginTrials namespace in line with Blink coding
    standards, and gets the test methods to match the corresponding methods
    in RuntimeEnabledFeatures.
    
    Change-Id: I2b91fbed4b675d55680996b101a110a98047091c
    Reviewed-on: https://chromium-review.googlesource.com/1135442
    Reviewed-by: Jason Chase <chasej@chromium.org>
    Reviewed-by: Jeremy Roman <jbroman@chromium.org>
    Commit-Queue: Ian Clelland <iclelland@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574715}

    Changed files

    • third_party/blink/renderer/bindings/scripts/generate_origin_trial_features.py
    • third_party/blink/renderer/bindings/scripts/v8_utilities.py
    • third_party/blink/renderer/bindings/tests/results/core/origin_trial_features_for_core.cc
    • third_party/blink/renderer/bindings/tests/results/core/v8_test_dictionary.cc
    • third_party/blink/renderer/build/scripts/templates/origin_trials.cc.tmpl
    • third_party/blink/renderer/build/scripts/templates/origin_trials.h.tmpl
    • third_party/blink/renderer/build/scripts/templates/web_origin_trials.cc.tmpl
    • third_party/blink/renderer/core/dom/document.cc
    • third_party/blink/renderer/core/dom/events/event_dispatcher.cc
    • third_party/blink/renderer/core/html/canvas/canvas_rendering_context.cc
    • third_party/blink/renderer/core/html/canvas/html_canvas_element.cc
    • third_party/blink/renderer/core/loader/document_loader.cc
    • third_party/blink/renderer/core/loader/subresource_integrity_helper.cc
    • third_party/blink/renderer/core/offscreencanvas/offscreen_canvas.cc
    • third_party/blink/renderer/core/testing/origin_trials_test.cc
    • third_party/blink/renderer/core/testing/v8/web_core_test_support.cc
    • third_party/blink/renderer/core/timing/window_performance.cc
    • third_party/blink/renderer/modules/gamepad/navigator_gamepad.cc
    • third_party/blink/renderer/modules/mediastream/media_stream_track.cc
    • third_party/blink/renderer/modules/mediastream/user_media_request.cc
    • third_party/blink/renderer/modules/modules_initializer.cc
    • third_party/blink/renderer/modules/peerconnection/rtc_peer_connection.cc
    • third_party/blink/renderer/modules/xr/xr_presentation_context.cc
  2. Fix wrong calculation of time on UsageTimeLimitProcessor.

    Changed by hgrandinettiohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:04:17 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 4e070c6b548e584a4e7934e88bcfb98a045518b1

    Comments

    Fix wrong calculation of time on UsageTimeLimitProcessor.
    
    The function that calculates wheter the time window limit of the current day is
    active, had a wrong logic.
    
    Bug: 860679
    Change-Id: Iafaaa54e36424033adaf384cdbc9c15d7aa2328e
    Reviewed-on: https://chromium-review.googlesource.com/1133459
    Reviewed-by: Jacob Dufault <jdufault@chromium.org>
    Reviewed-by: Alexander Alekseev <alemate@chromium.org>
    Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com>
    Cr-Commit-Position: refs/heads/master@{#574716}

    Changed files

    • chrome/browser/chromeos/child_accounts/usage_time_limit_processor.cc
    • chrome/browser/chromeos/child_accounts/usage_time_limit_processor_unittest.cc
  3. Handle MCVD cleanup properly if texture has been destroyed.

    Changed by liberatoohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:05:18 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision dcf09c7b1347f35a690e11fc7f592b678d5532db

    Comments

    Handle MCVD cleanup properly if texture has been destroyed.
    
    If AbstractTexture drops its reference to the underlying texture,
    then that texture might have been freed.  This happens when the
    gl stub is lost.
    
    Previously, MCVD assumed that the CodecImage attached to the texture
    was valid.  However, if the AbstractTexture has dropped its ref
    to the texture, and there are no other refs, then this assumption
    isn't right.
    
    This CL checks if the AbstractTexture still has a TextureBase before
    referencing the
    ...skip...
    ndered
    codec buffer.
    
    Bug: 863012
    Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
    Change-Id: If83a9eb0c27d6eb8e995424bdf71f7f7bc93590d
    Reviewed-on: https://chromium-review.googlesource.com/1135697
    Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
    Commit-Queue: Frank Liberato <liberato@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574717}

    Changed files

    • media/gpu/android/texture_pool.cc
    • media/gpu/android/video_frame_factory_impl.cc
  4. NUX Google Apps - Show page at startup.

    Changed by hcarmonaohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:07:58 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 8f2c3cb6d4923e8d5bc5486d9848fc9520e70a1d

    Comments

    NUX Google Apps - Show page at startup.
    
    Shows the page on start up if the NuxGoogleApps feature is enabled.
    
    Bug: 832938
    Change-Id: Ibec2d3cb15d8922d4b8d475dca71671a6a02878a
    Reviewed-on: https://chromium-review.googlesource.com/1115475
    Reviewed-by: Nico Weber <thakis@chromium.org>
    Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
    Reviewed-by: Tommy Martino <tmartino@chromium.org>
    Reviewed-by: Stefan Kuhne <skuhne@chromium.org>
    Reviewed-by: Lei Zhang <thestig@chromium.org>
    Commit-Queue: Hector Carmona <hcarmona@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574718}

    Changed files

    • BUILD.gn
    • chrome/browser/profiles/profile_manager.cc
    • chrome/browser/ui/BUILD.gn
    • chrome/browser/ui/startup/startup_browser_creator.cc
    • chrome/browser/ui/startup/startup_tab_provider.cc
    • chrome/browser/ui/startup/startup_tab_provider.h
    • chrome/browser/ui/startup/startup_tab_provider_unittest.cc
    • chrome/browser/ui/webui/welcome_ui.cc
    • chrome/browser/ui/webui/welcome_ui.h
    • chrome/common/DEPS
    • chrome/common/pref_names.cc
    • chrome/common/pref_names.h
    • components/nux_google_apps/BUILD.gn
    • components/nux_google_apps/constants.cc
    • components/nux_google_apps/constants.h
  5. Update V8 to version 6.9.353.

    Changed by v8-ci-autoroll-builderohnoyoudont@chops-service-accounts.iam.gserviceaccount.com
    Changed at Thursday, 12-Jul-18 21:11:03 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 56902fbf9cabbe2d659e36ff59cce3f25519bb1e

    Comments

    Update V8 to version 6.9.353.
    
    Summary of changes available at:
    https://chromium.googlesource.com/v8/v8/+log/8b17db68..6234bd45
    
    Please follow these instructions for assigning/CC'ing issues:
    https://github.com/v8/v8/wiki/Triaging%20issues
    
    Please close rolling in case of a roll revert:
    https://v8-roll.appspot.com/
    This only works with a Google account.
    
    CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tes
    ...skip...
    tional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel
    
    TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com
    
    Change-Id: If18a3fa6eca5568e52e21c64e3b31c5081e21300
    Reviewed-on: https://chromium-review.googlesource.com/1134599
    Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
    Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
    Cr-Commit-Position: refs/heads/master@{#574719}

    Changed files

    • DEPS
  6. RC: Use Chrome usage time since hidden to decide if tab can be proactively discarded.

    Changed by fdorayohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:11:50 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 3c279f295bc8924c82ed072f564ac9fe8fa3c8aa

    Comments

    RC: Use Chrome usage time since hidden to decide if tab can be proactively discarded.
    
    Previously, a tab was proactively discarded when it had spent T time hidden,
    where T depends on the number of non-discarded tabs and the amount of
    physical memory. Unfortunately, that meant that if a user kept Chrome
    open during the night without touching it, all hidden tabs were discarded
    in the morning.
    
    With this CL, we use the "Chrome usage time since hidden" to determine
    if a tab should be proactively discarded. That will prevent the unwanted
    behavior of finding all tabs discarded after a long period of inactivity.
    
    Bug: 775644
    Change-Id: Ie45ddfc07df782adeb32e3334a97bacaec429d45
    Reviewed-on: https://chromium-review.googlesource.com/1130470
    Commit-Queue: François Doray <fdoray@chromium.org>
    Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574720}

    Changed files

    • chrome/browser/resource_coordinator/tab_manager.cc
    • chrome/browser/resource_coordinator/tab_manager.h
    • chrome/browser/resource_coordinator/tab_manager_unittest.cc
  7. Fix TimeLimit notifications scheduled time.

    Changed by hgrandinettiohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:12:59 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 3e3bfb0e1c19b0fbc2321ee85724b7705106dc15

    Comments

    Fix TimeLimit notifications scheduled time.
    
    Bug: 860674
    Change-Id: Iac33adab459abf7bae5f4fae513eea5c06335412
    Reviewed-on: https://chromium-review.googlesource.com/1133460
    Reviewed-by: Jacob Dufault <jdufault@chromium.org>
    Reviewed-by: Alexander Alekseev <alemate@chromium.org>
    Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com>
    Cr-Commit-Position: refs/heads/master@{#574721}

    Changed files

    • chrome/browser/chromeos/child_accounts/screen_time_controller.cc
  8. [Android MR] Check Google Play services APK version before enabling CAF

    Changed by zqzhangohnoyoudont@google.com
    Changed at Thursday, 12-Jul-18 21:13:24 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 9b866113743ca04361daf9e63c30ae190ca60da4

    Comments

    [Android MR] Check Google Play services APK version before enabling CAF
    
    This CL checks GMS APK version before enabling CAF. The reason is that
    the current SDK version is 12.0.1, while we require the APK version to
    be 12.6.0 or above to make it fully functional (this is to avoid
    intializing the SDK in Activity#onCreate()).
    
    Currently we are using a fallback implementation to check GMS APK
    version. Ideally this should be done via the versioned
    GoogleApiAvailability.isGooglePlayServiceAvailable() API. H
    ...skip...
    a later version. The downstream
    implementation is calling the versioned API directly.
    
    After the upstream SDK version gets updated, we can just call the
    versioned API directly.
    
    Bug: 711860
    Change-Id: Iec5f84cffcc5c55fd303255b91a7f187c79b15cb
    Reviewed-on: https://chromium-review.googlesource.com/1132474
    Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
    Reviewed-by: Theresa <twellington@chromium.org>
    Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574722}

    Changed files

    • chrome/android/java/src/org/chromium/chrome/browser/AppHooks.java
    • chrome/android/java/src/org/chromium/chrome/browser/media/router/ChromeMediaRouter.java