Builder chromeos-daisy-rel Build 33451
Results:
Success
Trigger Info:
Project | chromium |
Revision | 5c8b5d95aa88a6898b52ed9ad9843d4c0ba4ff13 |
Got Revision | 5c8b5d95aa88a6898b52ed9ad9843d4c0ba4ff13 |
Execution:
- Source: Task 40818a7895e00910
- Bot: swarm1364-c4
Steps and Logfiles:
Show:-
( 106751 days 23 hrs ) Failed to fetch step information from LogDogLog stream has no annotation entries
- - no logs -
Build Properties:
Name | Value | Source |
---|
Blamelist:
- Tanja Gornak (melandoryohnoyoudont@chromium.org)
- Etienne Bergeron (etiennebohnoyoudont@chromium.org)
Timing:
Create | Friday, 12-Oct-18 14:40:41 UTC |
Start | Friday, 12-Oct-18 14:40:46 UTC |
End | Friday, 12-Oct-18 14:46:26 UTC |
Pending | 4 secs |
Execution | 5 mins 39 secs |
All Changes:
-
[Tango->FCM] Do not perform bulk unregistering on shutdown and on handler unregistering.
Changed by Tanja Gornak - melandoryohnoyoudont@chromium.org Changed at Friday, 12-Oct-18 14:39:54 UTC Repository https://chromium.googlesource.com/chromium/src Branch Revision 5c8b5d95aa88a6898b52ed9ad9843d4c0ba4ff13 Comments
[Tango->FCM] Do not perform bulk unregistering on shutdown and on handler unregistering. * The service shouldn't unregister from the topics, when handler the Handler is unregistering from topic (as stated in the documentation for for UnregisterHandler). * Sync shouldn't unregister on browser shutdown TBR=gab@chromium.org, pavely@chromium.org Bug: 894752, 801985 Change-Id: If676d159ba7d7beeebf325bce2e78b5847da3f76 Reviewed-on: https://chromium-review.googlesource.com/c/1277908 Reviewed-by: Tatiana Gornak <melandory@chromium.org> Reviewed-by: Gabriel Charette <gab@chromium.org> Commit-Queue: Tatiana Gornak <melandory@chromium.org> Cr-Commit-Position: refs/heads/master@{#599206}
Changed files
- chrome/browser/prefs/browser_prefs.cc
- components/invalidation/impl/BUILD.gn
- components/invalidation/impl/fcm_fake_invalidator.cc
- components/invalidation/impl/fcm_invalidation_listener.cc
- components/invalidation/impl/fcm_invalidation_listener.h
- components/invalidation/impl/fcm_invalidation_service.cc
- components/invalidation/impl/fcm_invalidation_service.h
- components/invalidation/impl/fcm_invalidation_service_unittest.cc
- components/invalidation/impl/invalidator_registrar.cc
- components/invalidation/impl/invalidator_registrar.h
- components/invalidation/impl/invalidator_registrar_with_memory.cc
- components/invalidation/impl/invalidator_registrar_with_memory.h
- components/invalidation/public/invalidation_util.h
- components/sync/driver/glue/sync_backend_host_impl.cc
-
Add trace events to investigate pathological fonts loading
Changed by Etienne Bergeron - etiennebohnoyoudont@chromium.org Changed at Friday, 12-Oct-18 14:33:56 UTC Repository https://chromium.googlesource.com/chromium/src Branch Revision 3638eaae091158d771e3ac8ce7d45c2ac925fb32 Comments
Add trace events to investigate pathological fonts loading This CL is adding trace events to look closer on some slow cases happening in the browser process. Traces will be collected via slow-reports and an investigation will be continued based on results of these events. R=fdoray@chromium.org, ccameron@chromium.org Bug: 894459 Change-Id: I2e3c37e9a42ceef9ca9aea5ec94a125db247aa77 Reviewed-on: https://chromium-review.googlesource.com/c/1277825 Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Reviewed-by: ccameron <ccameron@chromium.org> Reviewed-by: François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#599205}
Changed files
- ui/gfx/render_text_harfbuzz.cc