Home | Search | chromium - Builders
Login

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

Results:

Success

Trigger Info:

Projectchromium
Revisiondcf09c7b1347f35a690e11fc7f592b678d5532db
Got Revisiondcf09c7b1347f35a690e11fc7f592b678d5532db

Execution:

Steps and Logfiles:

Show:
  1. ( 338 ms ) setup_build
    running recipe: "chromium"
  2. ( 1 secs ) remove .cipd
  3. ( 50 secs ) bot_update
    [69GB/295GB used (23%)]
  4. ( 0 ) ensure_goma
  5. ( 745 ms ) swarming.py --version
    0.13
  6. ( 11 secs ) gclient runhooks
  7. ( 464 ms ) read test spec (chromium.gpu.json)
    path: /b/swarming/w/ir/cache/builder/src/testing/buildbot/chromium.gpu.json
  8. ( 4 secs ) clean local files
  9. ( 1 secs ) tree truth steps
  10. ( 28 secs ) generate_build_files
  11. ( 3 mins 45 secs ) compile
  12. ( 1 mins 20 secs ) isolate tests
  13. ( 601 ms ) find isolated tests
  14. ( 0 ) test_pre_run
  15. ( 2 mins 34 secs ) context_lost_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:44.405540
    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)
     
  16. ( 1 secs ) depth_capture_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:11.828190
    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)
     
  17. ( 43 secs ) gpu_process_launch_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:30.768460
    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)
     
  18. ( 1 secs ) hardware_accelerated_feature_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:10.233220
    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)
     
  19. ( 1 secs ) info_collection_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:01:54.392950
    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. ( 1 secs ) maps_pixel_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:02:19.791030
    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)
     
  21. ( 2 mins 22 secs ) pixel_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:05:55.889490
    Total tests: 46
    * Passed: 36 (36 expected, 0 unexpected)
    * Skipped: 10 (10 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  22. ( 1 secs ) screenshot_sync_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:06.705650
    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)
     
  23. ( 1 secs ) trace_test on Android device Nexus 5X
    Run on OS: 'Android'
    Shard duration: 0:03:24.851490
    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)
     
  24. ( 5 mins 24 secs ) webgl_conformance_tests on Android device Nexus 5X
    Run on OS: 'Android'
    Max shard duration: 0:11:16.511870 (shard #2)
    Min shard duration: 0:05:22.014620 (shard #5)
    Total tests: 922
    * Passed: 913 (913 expected, 0 unexpected)
    * Skipped: 9 (9 expected, 0 unexpected)
    * Failed: 0 (0 expected, 0 unexpected)
    * Flaky: 0 (0 expected, 0 unexpected)
     
  25. ( 294 ms ) Tests statistics
     
    Stats
    Total shards: 15
    Total runtime: 1:01:36.466105
     
  26. ( 314 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": 1531429689785750, "id": "8941173297561769088", "project": "chromium", "tags": ["builder:Android Release (Nexus 5X)", "buildset:commit/git/dcf09c7b1347f35a690e11fc7f592b678d5532db", "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/dcf09c7b1347f35a690e11fc7f592b678d5532db", "gitiles_ref:refs/heads/master", "scheduler_invocation_id:9106603359885124256", "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 7830 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 "dcf09c7b1347f35a690e11fc7f592b678d5532db" setup_build
got_angle_revision "5598148b761380773c4e650b5b67f47553b0f090" bot_update
got_buildtools_revision "0dd5c6f980d22be96b728155249df2da355989d9" bot_update
got_nacl_revision "e6ce828ef60c4c1438867b535efbbb5d9a177c0e" bot_update
got_revision "dcf09c7b1347f35a690e11fc7f592b678d5532db" bot_update
got_revision_cp "refs/heads/master@{#574717}" bot_update
got_swarming_client_revision "9a518d097dca20b7b00ce3bdfc5d418ccc79893a" bot_update
got_v8_revision "8b17db68f75a95d69debfa85b70aea3ec0766aaf" bot_update
got_v8_revision_cp "refs/heads/6.9.352@{#1}" bot_update
got_webrtc_revision "895617fa9bc36c240b37d47402cdb341ecadf994" bot_update
got_webrtc_revision_cp "refs/heads/master@{#23955}" bot_update
swarm_hashes_refs/heads/master(at){#574717}_without_patch {"telemetry_gpu_integration_test": "7d73191bf2634c7b47c3c08c51117792d477dd5c"} isolate tests
swarm_hashes {"telemetry_gpu_integration_test": "7d73191bf2634c7b47c3c08c51117792d477dd5c"} find isolated tests

Blamelist:

  1. liberato@chromium.org (liberatoohnoyoudont@chromium.org)
  2. Henrique Grandinetti (hgrandinettiohnoyoudont@chromium.org)
  3. Ian Clelland (iclellandohnoyoudont@chromium.org)
  4. Ken MacKay (kmackayohnoyoudont@chromium.org)
  5. Henrique Grandinetti (hgrandinettiohnoyoudont@chromium.org)
  6. Francois Doray (fdorayohnoyoudont@chromium.org)
  7. Nicolas Pena (npmohnoyoudont@chromium.org)
  8. Karan Bhatia (karandeepbohnoyoudont@chromium.org)

Timing:

Create Thursday, 12-Jul-18 21:08:09 UTC
Start Thursday, 12-Jul-18 21:08:12 UTC
End Thursday, 12-Jul-18 21:27:32 UTC
Pending 2 secs
Execution 19 mins 19 secs

All Changes:

  1. Handle MCVD cleanup properly if texture has been destroyed.

    Changed by liberato@chromium.org - 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 CodecImage.
    
    An alternate approach of holding a scoped_refptr to the CodecImage
    in the callback would also work, but might keep the CodecImage
    around longer than it should when the stub is destroyed.  This can
    hold the MediaCodec open longer if the CodecImage has an unrendered
    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
  2. Fix wrong calculation of time on UsageTimeLimitProcessor.

    Changed by Henrique Grandinetti - 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. Use standard uppercase names for OT test methods

    Changed by Ian Clelland - 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
  4. [Chromecast] Implement audio output redirection

    Changed by Ken MacKay - kmackayohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 21:01:07 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 3ff1556fabbdc61aaab8ee42eee5ae7d0bd0591f

    Comments

    [Chromecast] Implement audio output redirection
    
    Allow matching audio streams to be redirected to a different output.
    
    Bug: b/73284499
    Change-Id: I9eae9d945728e87a6cef299e24632f19860bc8e7
    Reviewed-on: https://chromium-review.googlesource.com/1130998
    Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
    Reviewed-by: Luke Halliwell <halliwell@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574714}

    Changed files

    • chromecast/media/cma/backend/BUILD.gn
    • chromecast/media/cma/backend/audio_fader.cc
    • chromecast/media/cma/backend/audio_fader.h
    • chromecast/media/cma/backend/audio_output_redirector.cc
    • chromecast/media/cma/backend/audio_output_redirector.h
    • chromecast/media/cma/backend/filter_group.cc
    • chromecast/media/cma/backend/filter_group_unittest.cc
    • chromecast/media/cma/backend/mixer_input.cc
    • chromecast/media/cma/backend/mixer_input.h
    • chromecast/media/cma/backend/mock_redirected_audio_output.cc
    • chromecast/media/cma/backend/mock_redirected_audio_output.h
    • chromecast/media/cma/backend/stream_mixer.cc
    • chromecast/media/cma/backend/stream_mixer.h
    • chromecast/media/cma/backend/stream_mixer_unittest.cc
    • chromecast/public/cast_media_shlib.h
    • chromecast/public/media/BUILD.gn
    • chromecast/public/media/redirected_audio_output.h
  5. Reset screen time when policy is set.

    Changed by Henrique Grandinetti - hgrandinettiohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 20:58:14 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 181e63453a3893703a891f072853e33be656a7bf

    Comments

    Reset screen time when policy is set.
    
    The used time should be reset once the time usage limit is set.
    
    Bug: 860676
    Change-Id: I1d9650d298041caf0b6c2f7321f8263727924b60
    Reviewed-on: https://chromium-review.googlesource.com/1134058
    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@{#574713}

    Changed files

    • chrome/browser/chromeos/child_accounts/screen_time_controller.cc
  6. RC: Record Chrome usage time when a LifecycleUnit is hidden.

    Changed by Francois Doray - fdorayohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 20:54:33 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 840dc0a7c0eacb82070efe833ef3aacc7b2e89cb

    Comments

    RC: Record Chrome usage time when a LifecycleUnit is hidden.
    
    With this CL, the total Chrome usage time measured by UsageClock is
    recorded in a LifecycleUnit when it is hidden. In an upcoming CL, this
    will be used to discard a LifecycleUnit after a given amount of Chrome
    usage time has elapsed since it was hidden.
    
    We also record the wall time when a LifecycleUnit is hidden, because
    freezing occurs when a LifeycleUnit has been hidden for a given amount
    of wall clock time, not Chrome usage time.
    
    Bug: 775644
    Change-Id: I76d504e9bbf3eb86ded1203e4e117086faf93277
    Reviewed-on: https://chromium-review.googlesource.com/1133593
    Commit-Queue: François Doray <fdoray@chromium.org>
    Reviewed-by: Scott Violet <sky@chromium.org>
    Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574712}

    Changed files

    • chrome/browser/browser_process_impl.cc
    • chrome/browser/browser_process_impl.h
    • chrome/browser/resource_coordinator/lifecycle_unit.h
    • chrome/browser/resource_coordinator/lifecycle_unit_base.cc
    • chrome/browser/resource_coordinator/lifecycle_unit_base.h
    • chrome/browser/resource_coordinator/lifecycle_unit_base_unittest.cc
    • chrome/browser/resource_coordinator/tab_lifecycle_unit.cc
    • chrome/browser/resource_coordinator/tab_lifecycle_unit.h
    • chrome/browser/resource_coordinator/tab_lifecycle_unit_source.cc
    • chrome/browser/resource_coordinator/tab_lifecycle_unit_source.h
    • chrome/browser/resource_coordinator/tab_lifecycle_unit_unittest.cc
    • chrome/browser/resource_coordinator/tab_manager.cc
    • chrome/browser/resource_coordinator/tab_manager.h
    • chrome/browser/resource_coordinator/tab_manager_stats_collector.cc
    • chrome/browser/resource_coordinator/test_lifecycle_unit.cc
    • chrome/browser/resource_coordinator/test_lifecycle_unit.h
    • chrome/test/base/testing_browser_process.cc
    • chrome/test/base/testing_browser_process.h
  7. Use UMA_HISTOGRAM_TIMES or saturated_cast to report milliseconds

    Changed by Nicolas Pena - npmohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 20:49:00 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 3e44f3be427bb7222e8e20640e261d620478e8bc

    Comments

    Use UMA_HISTOGRAM_TIMES or saturated_cast to report milliseconds
    
    This CL changes Blink code from using Count(delta.InMilliseconds()) to:
    * UMA_HISTOGRAM_TIMES where possible.
    * Otherwise, UMA_HISTOGRAM_CUSTOM_COUNTS if possible.
    * Otherwise, saturated_cast.
    
    Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
    Change-Id: I4f6e2ae0fb318b906ec75c546bea519cd130b09e
    Reviewed-on: https://chromium-review.googlesource.com/1134083
    Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
    Reviewed-by: Jeremy Roman <jbroman@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574711}

    Changed files

    • third_party/blink/renderer/core/editing/spellcheck/spell_check_requester.cc
    • third_party/blink/renderer/core/html/media/autoplay_uma_helper.cc
    • third_party/blink/renderer/core/html/parser/css_preload_scanner.cc
    • third_party/blink/renderer/modules/media_controls/elements/media_control_timeline_metrics.cc
    • third_party/blink/renderer/modules/notifications/notification_image_loader.cc
    • third_party/blink/renderer/platform/heap/heap_stats_collector.cc
    • third_party/blink/renderer/platform/heap/heap_stats_collector.h
    • third_party/blink/renderer/platform/heap/heap_stats_collector_test.cc
    • third_party/blink/renderer/platform/heap/thread_state.cc
    • third_party/blink/renderer/platform/scheduler/main_thread/main_thread_scheduler_impl.cc
  8. Change RulesMonitorService::HasRegisteredRuleset to take an extension_id.

    Changed by Karan Bhatia - karandeepbohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 20:47:42 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision b96ae12ef5fa70c2389e5b23da5a924eb4dff359

    Comments

    Change RulesMonitorService::HasRegisteredRuleset to take an extension_id.
    
    This CL changes RulesMonitorService::HasRegisteredRuleset to take an
    extension_id instead of an extension pointer.
    
    BUG=None
    
    Change-Id: If6d220b7bcaf9be473ff819961f5ed9fe67f681f
    Reviewed-on: https://chromium-review.googlesource.com/1134519
    Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
    Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574710}

    Changed files

    • extensions/browser/api/declarative_net_request/declarative_net_request_api.cc
    • extensions/browser/api/declarative_net_request/rules_monitor_service.cc
    • extensions/browser/api/declarative_net_request/rules_monitor_service.h