Home | Search | chromium - Builders
Login

Builder Android Release (Nexus 5X) Build 9096 Canonical Ubuntu

Results:

Success

Trigger Info:

Projectchromium
Revision31322898bc81e2e07e3d9f89aa051a60c5f93215
Got Revision31322898bc81e2e07e3d9f89aa051a60c5f93215

Execution:

Steps and Logfiles:

Show:
  1. ( 312 ms ) setup_build
    running recipe: "chromium"
  2. ( 44 secs ) bot_update
    [71GB/295GB used (24%)]
  3. ( 0 ) ensure_goma
  4. ( 836 ms ) swarming.py --version
    0.13
  5. ( 13 secs ) gclient runhooks
  6. ( 561 ms ) read test spec (chromium.gpu.json)
    path: /b/swarming/w/ir/cache/builder/src/testing/buildbot/chromium.gpu.json
  7. ( 4 secs ) clean local files
  8. ( 87 ms ) tree truth steps
  9. ( 33 secs ) generate_build_files
  10. ( 1 mins 32 secs ) compile
  11. ( 28 secs ) isolate tests
  12. ( 649 ms ) find isolated tests
  13. ( 0 ) test_pre_run
  14. ( 2 mins 42 secs ) context_lost_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:55.593930
    Total tests: 8
    * Passed: 5 (5 expected, 0 unexpected)
    * Skipped: 3 (3 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  15. ( 1 secs ) depth_capture_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:05.501640
    Total tests: 3
    * Passed: 3 (3 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  16. ( 1 mins 23 secs ) gpu_process_launch_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:04:20.011960
    Total tests: 15
    * Passed: 15 (15 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  17. ( 1 secs ) hardware_accelerated_feature_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:01:44.202850
    Total tests: 2
    * Passed: 2 (2 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  18. ( 1 secs ) info_collection_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:01:35.068940
    Total tests: 1
    * Passed: 1 (1 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  19. ( 1 secs ) maps_pixel_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:33.643590
    Total tests: 1
    * Passed: 1 (1 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  20. ( 6 mins 24 secs ) pixel_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:10:42.385980
    Total tests: 48
    * Passed: 38 (38 expected, 0 unexpected)
    * Skipped: 10 (10 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  21. ( 1 secs ) screenshot_sync_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:20.479340
    Total tests: 4
    * Passed: 4 (4 expected, 0 unexpected)
    * Skipped: 0 (0 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  22. ( 1 secs ) trace_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:18.288230
    Total tests: 34
    * Passed: 17 (17 expected, 0 unexpected)
    * Skipped: 17 (17 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  23. ( 6 mins 34 secs ) webgl_conformance_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Max shard duration: 0:17:26.104230 (shard #2)
    Min shard duration: 0:05:49.301150 (shard #5)
    Total tests: 924
    * Passed: 915 (915 expected, 0 unexpected)
    * Skipped: 9 (9 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  24. ( 348 ms ) Tests statistics
     
    Stats
    Total shards: 15
    Total runtime: 1:25:35.307830
     
  25. ( 364 ms ) test_report

Build Properties:

NameValueSource
$recipe_engine/path {"cache_dir": "/b/swarming/w/ir/cache", "temp_dir": "/b/swarming/w/ir/tmp/rt"} setup_build
$recipe_engine/runtime {"is_experimental": false, "is_luci": true} setup_build
bot_id "swarm236-c4" setup_build
branch "refs/heads/master" setup_build
buildbucket {"build": {"bucket": "luci.chromium.ci", "created_by": "user:luci-scheduler@appspot.gserviceaccount.com", "created_ts": 1533969870089350, "id": "8938509725459936272", "project": "chromium", "tags": ["builder:Android Release (Nexus 5X)", "buildset:commit/git/31322898bc81e2e07e3d9f89aa051a60c5f93215", "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/31322898bc81e2e07e3d9f89aa051a60c5f93215", "gitiles_ref:refs/heads/master", "scheduler_invocation_id:9103939787668674880", "scheduler_job_id:chromium/Android Release (Nexus 5X)", "user_agent:luci-scheduler"]}, "hostname": "cr-buildbucket.appspot.com"} setup_build
buildername "Android Release (Nexus 5X)" setup_build
buildnumber 9096 setup_build
mastername "chromium.gpu" setup_build
path_config "generic" setup_build
recipe "chromium" setup_build
repository "https://chromium.googlesource.com/chromium/src.git" setup_build
revision "31322898bc81e2e07e3d9f89aa051a60c5f93215" setup_build
got_angle_revision "ea926a362b7748679d72bd56780d29c2ff20fd27" bot_update
got_buildtools_revision "9a90d9aaadeb5e04327ed05775f45132e4b3523f" bot_update
got_nacl_revision "96088f46727b75b2f6a24e1b62e5cc59ddb4612d" bot_update
got_revision "31322898bc81e2e07e3d9f89aa051a60c5f93215" bot_update
got_revision_cp "refs/heads/master@{#582433}" bot_update
got_swarming_client_revision "486c9b53c4d54dd4b95bb6ce0e31160e600dfc11" bot_update
got_v8_revision "4fe3de13fc5c2592559bb5e49e1a81a6d09a2efd" bot_update
got_v8_revision_cp "refs/heads/7.0.193@{#2}" bot_update
got_webrtc_revision "f5f5373372584fdcbf658a5c11ec28242c7fcd5e" bot_update
got_webrtc_revision_cp "refs/heads/master@{#24263}" bot_update
swarm_hashes_refs/heads/master(at){#582433}_without_patch {"telemetry_gpu_integration_test": "73007eb076227780737d894728457ad7f3231b62"} isolate tests
swarm_hashes {"telemetry_gpu_integration_test": "73007eb076227780737d894728457ad7f3231b62"} find isolated tests

Blamelist:

  1. David Roger (drogerohnoyoudont@chromium.org)
  2. Peter Kasting (pkastingohnoyoudont@chromium.org)

Timing:

Create Saturday, 11-Aug-18 06:44:30 UTC
Start Saturday, 11-Aug-18 06:44:33 UTC
End Saturday, 11-Aug-18 07:07:00 UTC
Pending 3 secs
Execution 22 mins 27 secs

All Changes:

  1. [Settings] UserEvents depends on history and passphrase

    Changed by David Roger - drogerohnoyoudont@chromium.org
    Changed at Saturday, 11-Aug-18 06:43:35 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 31322898bc81e2e07e3d9f89aa051a60c5f93215

    Comments

    [Settings] UserEvents depends on history and passphrase
    
    This is a reland of:
    https://chromium-review.googlesource.com/1170202
    
    which was reverted because of missing svg icon.
    
    The user events UI toggle should be grayed out and turned off
    when there is a passphrase or when history sync is disabled.
    Note that this is purely a UI change: the internal sync datatype
    is not really turned off in that case, and we assume that the Sync
    engines will correctly stop syncing user events in these cases,
    even if the preference is still ON.
    
    Bug: 865522, 865537
    Change-Id: I745f048b3ca301231f57c04b82d0d9d82a6f3b90
    Reviewed-on: https://chromium-review.googlesource.com/1170825
    Reviewed-by: Scott Chen <scottchen@chromium.org>
    Commit-Queue: David Roger <droger@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#582433}

    Changed files

    • chrome/browser/resources/settings/people_page/sync_browser_proxy.js
    • chrome/browser/resources/settings/people_page/sync_page.html
    • chrome/browser/resources/settings/people_page/sync_page.js
    • chrome/test/data/webui/settings/people_page_sync_page_test.js
  2. Revert "Change the history state throttle interval from 60 to 120 Hz."

    Changed by Peter Kasting - pkastingohnoyoudont@chromium.org
    Changed at Saturday, 11-Aug-18 05:51:46 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 5823b44aa85c3e803530cc77e9bd7429d523c575

    Comments

    Revert "Change the history state throttle interval from 60 to 120 Hz."
    
    This reverts commit 8e4127dd506c501cd3f51d91dc22a3dfa8f5f1ca.
    
    Reason for revert: Part 1 of trying to revert the history throttling changes, to see if https://bugs.chromium.org/p/chromium/issues/detail?id=870861 improves.
    
    Original change's description:
    > Change the history state throttle interval from 60 to 120 Hz.
    > 
    > This is a bit more lenient and may enable some callers, including a flaky test,
    > to get (more of) what they need. The test's root problem seems to be data races
    > (see issue 847326), however.
    > 
    > Bug: 870861
    > Change-Id: I249e9f06fa9a9a9f3b74e53cf2ef3f34b0c2371c
    > Reviewed-on: https://chromium-review.googlesource.com/1171825
    > Reviewed-by: Daniel Cheng <dcheng@chromium.org>
    > Commit-Queue: Chris Palmer <palmer@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#582415}
    
    TBR=palmer@chromium.org,dcheng@chromium.org,kinuko@chromium.org
    
    Change-Id: I9fb7b5b0f8ebff8b6d6c5a772745cfd2c10ef51a
    No-Presubmit: true
    No-Tree-Checks: true
    No-Try: true
    Bug: 870861
    Reviewed-on: https://chromium-review.googlesource.com/1171708
    Reviewed-by: Peter Kasting <pkasting@chromium.org>
    Commit-Queue: Peter Kasting <pkasting@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#582432}

    Changed files

    • third_party/blink/renderer/core/frame/history.cc