Back to build
Raw log | Switch to full mode | Login

/b/swarming/w/ir/cache/builder/src/build/tree_truth.sh /b/swarming/w/ir/cache/builder/src src in dir /b/swarming/w/ir/k: allow_subannotations: False cmd: ['/b/swarming/w/ir/cache/builder/src/build/tree_truth.sh', '/b/swarming/w/ir/cache/builder/src', 'src'] env: {'CHROME_HEADLESS': '1'} env_prefixes: {} env_suffixes: {} infra_step: False name_tokens: ('tree truth steps',) ok_ret: frozenset([0]) trigger_specs: () full environment: ADDRFAM: inet BOTO_CONFIG: /b/swarming/w/ir/tmp/gsutil_task/.boto BUILDBUCKET_EXPERIMENTAL: FALSE CHROME_HEADLESS: 1 CIPD_CACHE_DIR: /b/swarming/cipd_cache/cache CIPD_PROTOCOL: v2 DEVSHELL_CLIENT_PORT: 33856 DOCKER_CONFIG: /b/swarming/w/ir/tmp/docker_cfg_task DOCKER_TMPDIR: /b/swarming/w/ir/tmp/docker_tmp_task GIT_CONFIG_NOSYSTEM: 1 GIT_TERMINAL_PROMPT: 0 HOME: /home/chrome-bot IFACE: eth0 INFRA_GIT_WRAPPER_HOME: /b/swarming/w/ir/tmp/git_home_task LOGDOG_COORDINATOR_HOST: logs.chromium.org LOGDOG_STREAM_PREFIX: buildbucket/cr-buildbucket.appspot.com/8918452652472477904 LOGDOG_STREAM_PROJECT: chromium LOGDOG_STREAM_SERVER_PATH: unix:/b/swarming/w/ir/tmp/ld.sock LOGICAL: eth0 LUCI_CONTEXT: /b/swarming/w/itlmcV_Z/luci_context.468873301 MAC_CHROMIUM_TMPDIR: /b/swarming/w/ir/tmp/t METHOD: dhcp NO_GCE_CHECK: False PATH: /b/swarming/w/ir/cipd_bin_packages:/b/swarming/w/ir/cipd_bin_packages/bin:/b/swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PWD: /b/swarming/w/ir/k PYTHONIOENCODING: UTF-8 PYTHONUNBUFFERED: 1 ROOT_SETUP_LOG: /var/log/messages/chromebuild/root-setup.log SHLVL: 1 STARTUP_LOG: /var/log/messages/chromebuild/startup.log SWARMING_BOT_ID: swarm572-c4 SWARMING_EXTERNAL_BOT_SETUP: 1 SWARMING_HEADLESS: 1 SWARMING_SERVER: https://chromium-swarm.appspot.com SWARMING_TASK_ID: 43b4a909b3980d11 TEMP: /b/swarming/w/ir/tmp/t TEMPDIR: /b/swarming/w/ir/tmp/t TERM: linux TMP: /b/swarming/w/ir/tmp/t TMPDIR: /b/swarming/w/ir/tmp/t UPSTART_EVENTS: net-device-up UPSTART_INSTANCE: UPSTART_JOB: chromebuild-startup USER: chrome-bot USERNAME: chrome-bot VPYTHON_VIRTUALENV_ROOT: /b/swarming/w/ir/cache/vpython _: /b/swarming/w/ir/cipd_bin_packages/vpython !@@@BUILD_STEP Brief summary of recent CLs in every branch@@@ src: 486a2d0f5ac4f1dc7b9933905e33a6326c7e24bc Associate v8::Isolate to blink::scheduler::ThreadScheduler tzik, Wed Mar 20 15:58:49 2019 +0000 cd7415d33a5966a419db27ee2a6bd8585a53b08a Launch.Modes never expires Brian White, Wed Mar 20 15:57:42 2019 +0000 828f945623ed7112955b4ee04e0aba50b9f85031 aw: Fix feature switch memory access Bo Liu, Wed Mar 20 15:57:15 2019 +0000 5064860ccf5ed15eab9aed04763e7426b0b41e0c TaskScheduler: Remove LazyStalenessPolicy from IntrusiveHeap Aditya Keerthi, Wed Mar 20 15:56:38 2019 +0000 0d74933969feafdbd275192a10647e74fef56489 Roll src-internal 9d3e8ca31939..9a3f4c19e779 (2 commits) chromium-internal-autoroll, Wed Mar 20 15:54:51 2019 +0000 5a8df75f6a2eb4ae3b97a0ddc31720d1b8f846a3 Turn off Clip Rect caching for elements under sticky positioned elements Mason Freed, Wed Mar 20 15:53:30 2019 +0000 8fcea262577f2ef932acb86af340e29acbb94982 Check temporarily_hidden() earlier as diagnostic. W. James MacLean, Wed Mar 20 15:48:03 2019 +0000 ead1bc234c633d8727fb3789a966ebdaad255008 Roll src/third_party/swiftshader 3e485a4f3ec8..5851ef46d285 (1 commits) chromium-autoroll, Wed Mar 20 15:46:51 2019 +0000 02658c705ef508cca9c57dcf7a9a737509e761f6 Extract out some objects owned by IdentityManagerDependenciesOwner. Lowell Manners, Wed Mar 20 15:41:17 2019 +0000 066d68c08e823117b117041499cb8d7a8b47caa9 CrOS Shelf: Let the focus ring "shrink wrap" control button shape Manu Cornet, Wed Mar 20 15:34:16 2019 +0000 ================================================================= !@@@BUILD_STEP New commits in repo src@@@ commit 486a2d0f5ac4f1dc7b9933905e33a6326c7e24bc Author: tzik <tzik@chromium.org> Date: Wed Mar 20 15:58:49 2019 +0000 Associate v8::Isolate to blink::scheduler::ThreadScheduler This adds v8::Isolate to ThreadSchedulerImpl and associates the isolate on its initialization, so that TaskQueue implementations can use it. Change-Id: I5feaed611e9ab5571f9c7b91fe9d063b6bb66aa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1517433 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by: Alexander Timin <altimin@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#642529} third_party/blink/renderer/bindings/core/v8/v8_initializer.cc | 1 + third_party/blink/renderer/core/dom/idle_deadline_test.cc | 2 ++ .../renderer/core/dom/scripted_idle_task_controller_test.cc | 2 ++ .../blink/renderer/core/workers/worker_backing_thread.cc | 8 +++++--- .../platform/scheduler/common/simple_thread_scheduler.h | 2 ++ .../renderer/platform/scheduler/common/thread_scheduler_impl.h | 10 ++++++++++ .../renderer/platform/scheduler/public/thread_scheduler.h | 7 +++++++ .../platform/scheduler/test/renderer_scheduler_test_support.cc | 1 + 8 files changed, 30 insertions(+), 3 deletions(-) commit cd7415d33a5966a419db27ee2a6bd8585a53b08a Author: Brian White <bcwhite@chromium.org> Date: Wed Mar 20 15:57:42 2019 +0000 Launch.Modes never expires Bug: 923083 Change-Id: I9c6e85046eea7e4b5ec14135844760964f6f1468 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1529188 Auto-Submit: Brian White <bcwhite@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#642528} tools/metrics/histograms/histograms.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) commit 828f945623ed7112955b4ee04e0aba50b9f85031 Author: Bo Liu <boliu@chromium.org> Date: Wed Mar 20 15:57:15 2019 +0000 aw: Fix feature switch memory access StringPiece only holds pointers to another piece of memory. And FeatureList::SplitFeatureListString explicitly warns the returned StringPieces point to the argument. So in previous code, if CommandLine already had enable/disable switches, the saved StringPiece was pointing to temporary memory. Bug: 943926 Change-Id: I7c7708dab7e0c81b9568bb1ffa22533fe4bf3b76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1532341 Commit-Queue: Bo <boliu@chromium.org> Reviewed-by: Tim Volodine <timvolodine@chromium.org> Cr-Commit-Position: refs/heads/master@{#642527} .../browser/scoped_add_feature_flags.cc | 16 ++++--- android_webview/browser/scoped_add_feature_flags.h | 6 +-- .../browser/scoped_add_feature_flags_unittests.cc | 49 ++++++++++++++++++++++ android_webview/test/BUILD.gn | 1 + 4 files changed, 63 insertions(+), 9 deletions(-) commit 5064860ccf5ed15eab9aed04763e7426b0b41e0c Author: Aditya Keerthi <adityakeerthi@google.com> Date: Wed Mar 20 15:56:38 2019 +0000 TaskScheduler: Remove LazyStalenessPolicy from IntrusiveHeap LazyStalenessPolicy was initially introduced to IntrusiveHeap in order to address the issue of cancelled tasks remaining on the DelayedTaskHeap. In practice, this approach found 0 cancelled tasks on the DelayedTaskHeap in over 99% of cases. This could indicate a flawed strategy in detecting cancelled tasks, or that there is not a significant number of cancelled tasks remaining on the DelayedTaskHeap. In either case, the LazyStalenessPolicy provides no benefit to TaskScheduler. Bug: 900191 Change-Id: I8ac94fdb214d822c607e9ce3751b706620f34d91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1521453 Reviewed-by: Jesse Doherty <jwd@chromium.org> Reviewed-by: Fran├žois Doray <fdoray@chromium.org> Reviewed-by: Alex Clarke <alexclarke@chromium.org> Commit-Queue: Aditya Keerthi <adityakeerthi@google.com> Cr-Commit-Position: refs/heads/master@{#642526} base/BUILD.gn | 3 - base/task/common/intrusive_heap.h | 49 +-- .../common/intrusive_heap_lazy_staleness_policy.h | 56 --- ...ntrusive_heap_lazy_staleness_policy_unittest.cc | 403 --------------------- base/task/common/intrusive_heap_unittest.cc | 67 ++-- base/task/common/test_utils.h | 38 -- base/task/task_scheduler/delayed_task_manager.cc | 35 -- base/task/task_scheduler/delayed_task_manager.h | 17 +- .../delayed_task_manager_unittest.cc | 13 - base/task/task_scheduler/task_scheduler_impl.cc | 1 - tools/metrics/histograms/histograms.xml | 15 +- 11 files changed, 64 insertions(+), 633 deletions(-) commit 0d74933969feafdbd275192a10647e74fef56489 Author: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Date: Wed Mar 20 15:54:51 2019 +0000 Roll src-internal 9d3e8ca31939..9a3f4c19e779 (2 commits) https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9d3e8ca31939..9a3f4c19e779 Created with: gclient setdep -r src-internal@9a3f4c19e779 The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=ksakamoto@chromium.org,mmentovai@chromium.org,carlosk@chromium.org,hendrich@chromium.org Change-Id: Ic677b66cafc2da3e161b670cfcd1d874af752082 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531519 Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#642525} DEPS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 5a8df75f6a2eb4ae3b97a0ddc31720d1b8f846a3 Author: Mason Freed <masonfreed@chromium.org> Date: Wed Mar 20 15:53:30 2019 +0000 Turn off Clip Rect caching for elements under sticky positioned elements For elements inside sticky positioned containers that were scrolled, the cached clip rect did not previously update the scroll position. That meant that the clip rect did not move with the contents, resulting in incorrect overlap checks in some cases. To fix this, we have to turn off caching for elements inside sticky positioned elements, because in that case the scroll is sometimes included and sometimes not, depending on whether the sticky constraint is binding. Bug: 942097, 931853, 935525 Change-Id: Ibd5810c23c8d92b6047709ed06f832acd4770a0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1526680 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#642524} .../compositing/compositing_inputs_updater.cc | 16 +++- .../paint/compositing/compositing_inputs_updater.h | 1 + .../blink/renderer/core/paint/paint_layer.h | 1 + .../core/paint/paint_layer_clipper_test.cc | 88 ++++++++++++++++++++++ ...ion-sticky-scroll-with-clip-and-abspos-ref.html | 33 ++++++++ ...osition-sticky-scroll-with-clip-and-abspos.html | 33 ++++++++ 6 files changed, 170 insertions(+), 2 deletions(-) commit 8fcea262577f2ef932acb86af340e29acbb94982 Author: W. James MacLean <wjmaclean@chromium.org> Date: Wed Mar 20 15:48:03 2019 +0000 Check temporarily_hidden() earlier as diagnostic. To assist debugging the flakiness of BasicSelectionIsolatedScrollMainframe it would be nice to confirm the value of temporarily_hidden() is correct prior to checking the active status. TBR=kenrb@chromium.org Bug: 805017 Change-Id: Iff9f35c01b8d92429514c5c5b5f771ea7c0d9c87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1532149 Reviewed-by: James MacLean <wjmaclean@chromium.org> Commit-Queue: James MacLean <wjmaclean@chromium.org> Cr-Commit-Position: refs/heads/master@{#642523} .../input/touch_selection_controller_client_aura_browsertest.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit ead1bc234c633d8727fb3789a966ebdaad255008 Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Date: Wed Mar 20 15:46:51 2019 +0000 Roll src/third_party/swiftshader 3e485a4f3ec8..5851ef46d285 (1 commits) https://swiftshader.googlesource.com/SwiftShader.git/+log/3e485a4f3ec8..5851ef46d285 git log 3e485a4f3ec8..5851ef46d285 --date=short --no-merges --format='%ad %ae %s' 2019-03-20 capn@google.com Don't treat SIMD::Float preferentially Created with: gclient setdep -r src/third_party/swiftshader@5851ef46d285 The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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 TBR=swiftshader-team+autoroll@chromium.org Change-Id: Ibc0fb45719847904babf101586cc50d778cd0ca9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531518 Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#642522} DEPS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Updated tag 'tree_truth' (was 02658c705ef5)