Home | Search | chromium - Builders

Builder Linux FYI dEQP Release (NVIDIA) Build 19378 Canonical Ubuntu



Trigger Info:

Got Revision0720b0228d5da8605132b93c3c5c989e5d3b8db1


Steps and Logfiles:

  1. ( 299 ms ) setup_build
    running recipe: "chromium"
  2. ( 451 ms ) remove .cipd
  3. ( 20 secs ) bot_update
    [45GB/295GB used (15%)]
  4. ( 0 ) ensure_goma
  5. ( 581 ms ) swarming.py --version
  6. ( 10 secs ) gclient runhooks
  7. ( 1 secs ) read test spec (chromium.gpu.fyi.json)
    path: /b/swarming/w/ir/cache/builder/src/testing/buildbot/chromium.gpu.fyi.json
  8. ( 488 ms ) build directory
  9. ( 6 secs ) extract build
  10. ( 433 ms ) find isolated tests
  11. ( 0 ) test_pre_run
  12. ( 2 secs ) angle_deqp_egl_gl_tests on NVIDIA GPU on Linux on Ubuntu
    Run on OS: 'Ubuntu'
    Max shard duration: 14s (shard #1)
    Min shard duration: 11s (shard #0)
  13. ( 12 secs ) angle_deqp_gles2_gl_tests on NVIDIA GPU on Linux on Ubuntu
    Run on OS: 'Ubuntu'
    Max shard duration: 41s (shard #1)
    Min shard duration: 34s (shard #0)
  14. ( 42 secs ) angle_deqp_gles31_gl_tests on NVIDIA GPU on Linux on Ubuntu
    Run on OS: 'Ubuntu'
    Max shard duration: 0:02:01.666030 (shard #4)
    Min shard duration: 0:01:05.838240 (shard #2)
  15. ( 35 secs ) angle_deqp_gles3_gl_tests on NVIDIA GPU on Linux on Ubuntu
    Run on OS: 'Ubuntu'
    Max shard duration: 0:01:06.051060 (shard #10)
    Min shard duration: 51s (shard #5)
  16. ( 727 ms ) Tests statistics
    Total shards: 26
    Total runtime: 0:21:28.280600

Build Properties:

$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 "swarm1077-c4" setup_build
buildbucket {"build": {"bucket": "luci.chromium.ci", "created_by": "user:luci-scheduler@appspot.gserviceaccount.com", "created_ts": 1531414847640120, "id": "8941188860679674304", "project": "chromium", "tags": ["builder:Linux FYI dEQP Release (NVIDIA)", "buildset:commit/gitiles/chromium.googlesource.com/chromium/src/+/0720b0228d5da8605132b93c3c5c989e5d3b8db1", "gitiles_ref:refs/heads/master", "parent_buildername:GPU FYI Linux dEQP Builder", "parent_buildnumber:27295", "scheduler_invocation_id:9106618922889606368", "scheduler_job_id:chromium/Linux FYI dEQP Release (NVIDIA)", "user_agent:luci-scheduler", "user_agent:recipe"]}, "hostname": "cr-buildbucket.appspot.com"} setup_build
buildername "Linux FYI dEQP Release (NVIDIA)" setup_build
buildnumber 19378 setup_build
mastername "chromium.gpu.fyi" setup_build
parent_buildername "GPU FYI Linux dEQP Builder" setup_build
parent_got_angle_revision "9ff9c7732a8731cac249127ee68f1f5f02d8eb63" setup_build
parent_got_buildtools_revision "0dd5c6f980d22be96b728155249df2da355989d9" setup_build
parent_got_nacl_revision "e6ce828ef60c4c1438867b535efbbb5d9a177c0e" setup_build
parent_got_revision "0720b0228d5da8605132b93c3c5c989e5d3b8db1" setup_build
parent_got_revision_cp "refs/heads/master@{#574603}" setup_build
parent_got_swarming_client_revision "9a518d097dca20b7b00ce3bdfc5d418ccc79893a" setup_build
parent_got_v8_revision "8b17db68f75a95d69debfa85b70aea3ec0766aaf" setup_build
parent_got_v8_revision_cp "refs/heads/6.9.352@{#1}" setup_build
parent_got_webrtc_revision "58c79f66dd3afef0ec2d77053e44f26b998b84b1" setup_build
parent_got_webrtc_revision_cp "refs/heads/master@{#23950}" setup_build
parent_mastername "chromium.gpu.fyi" setup_build
path_config "generic" setup_build
recipe "chromium" setup_build
revision "0720b0228d5da8605132b93c3c5c989e5d3b8db1" setup_build
got_angle_revision "5598148b761380773c4e650b5b67f47553b0f090" bot_update
got_buildtools_revision "0dd5c6f980d22be96b728155249df2da355989d9" bot_update
got_nacl_revision "e6ce828ef60c4c1438867b535efbbb5d9a177c0e" bot_update
got_revision "0720b0228d5da8605132b93c3c5c989e5d3b8db1" bot_update
got_revision_cp "refs/heads/master@{#574603}" 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 "58c79f66dd3afef0ec2d77053e44f26b998b84b1" bot_update
got_webrtc_revision_cp "refs/heads/master@{#23950}" bot_update
swarm_hashes {"angle_deqp_egl_tests": "fc20499632ae78345501f0ffda74b8eca92b7790", "angle_deqp_gles2_tests": "33d5c4f890e07de515aaeb58928ff78dcbe1c523", "angle_deqp_gles31_tests": "62d7edc460e8d9feb00c263ae916ef3f33ef15d2", "angle_deqp_gles3_tests": "82eecca4f0c259634c4f29ca93d3103e103e5e28"} find isolated tests


  1. Colin Blundell (blundellohnoyoudont@chromium.org)


Create Thursday, 12-Jul-18 17:00:47 UTC
Start Thursday, 12-Jul-18 17:00:49 UTC
End Thursday, 12-Jul-18 17:05:15 UTC
Pending 2 secs
Execution 4 mins 25 secs

All Changes:

  1. Revert "Have Device Service observe MessageLoop destruction"

    Changed by Colin Blundell - blundellohnoyoudont@chromium.org
    Changed at Thursday, 12-Jul-18 16:53:32 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Revision 0720b0228d5da8605132b93c3c5c989e5d3b8db1


    Revert "Have Device Service observe MessageLoop destruction"
    This reverts commit 8e9dbcd3188c015f2dd67ba781168431aa51dab5.
    Reason for revert: It turns out that this is not the right solution to the problem. crbug.com/856771 presents a crash that this CL introduces on ChromeOS: the Device Service instance is now shut down after the DBusThreadManager global instance, on which it implicitly depends. We'll have to be more precise about the timing of when the Device Service instance is destroyed, which will mean doing the plumbing that the below CL was looking to avoid. This is all sad-making, but c'est la vie.
    Bug: 856771, 794105
    Original change's description:
    > Have Device Service observe MessageLoop destruction
    > The Device Service needs to clean up parts of its internal state as part
    > of browser shutdown. However, it also needs to run on the UI thread,
    > and embedded services that run on the UI thread are not guaranteed to
    > be destroyed as part of browser shutdown (tasks to destroy these
    > services are posted from the IO thread by
    > ServiceManagerConnectionImpl::ShutDownOnIOThread, but the UI thread is
    > typically shut down before these posted tasks are run).
    > To solve this issue we discussed adding plumbing wherein embedded
    > services could inform //content that they wanted to be notified when
    > shutdown was occurring on the main thread. However, on investigation
    > this plumbing would be painful to implement: it is only
    > EmbeddedInstanceManager that has direct information of these service
    > instances, and that object lives far away from //content's
    > ServiceManagerContext, the object that knows when shutdown is occurring
    > on the main thread.
    > This CL takes an alternative approach of having the Device Service
    > implementation observe the destruction of its MessageLoop. I have
    > verified that the observation is triggered on shutdown of Chrome.
    > Bug: 794105
    > Change-Id: I3b383871679d42f544812be4bcb13c872cf276ff
    > Reviewed-on: https://chromium-review.googlesource.com/1099245
    > Commit-Queue: Colin Blundell <blundell@chromium.org>
    > Reviewed-by: Ken Rockot <rockot@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#567260}
    # Not skipping CQ checks because original CL landed > 1 day ago.
    Bug: 794105
    Change-Id: I6de862f5828560ea903855898e09322e9f8d1e6c
    Reviewed-on: https://chromium-review.googlesource.com/1134887
    Commit-Queue: Colin Blundell <blundell@chromium.org>
    Reviewed-by: Colin Blundell <blundell@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#574603}

    Changed files

    • services/device/device_service.cc
    • services/device/device_service.h