GitLab

https://android.googlesource.com/platform/external/perfetto.git/+log/5d2918e8ee83..e6dfe41ffa6e


git log 5d2918e8ee83..e6dfe41ffa6e --date=short --no-merges --format='%ad %ae %s'
2018-09-20 hjd@google.com perfetto-ui: Rename rawQuery to query
2018-09-20 hjd@google.com Merge "perfetto-ui: Remove engine worker proxy hacks"


Created with:
  gclient setdep -r src/third_party/perfetto@e6dfe41ffa6e

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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.


TBR=perfetto-bugs@google.com

Change-Id: I524fc5b7b49b9ec91b5d513f48d0344d937e38c2
Reviewed-on: https://chromium-review.googlesource.com/1236474Reviewed-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@{#592833}

The SelectableListToolbar is setting FocusInTouchMode to
true for all its children. This is problematic for the Done
button, as it then requires two taps to click.

Also, while I was at it, use the same styling for the Done
button as the Done button in the Contacts Picker.

Bug: 813422, 656015
Change-Id: I277626563885621b3bf677697d464a3299e6658f
Reviewed-on: https://chromium-review.googlesource.com/1236435
Commit-Queue: Finnur Thorarinsson <finnur@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592832}

Skip GLImageNativePixmap tests and GLSurfaceEGLTest.SurfaceFormatTest
for MSAN.

TBR=kbr

Bug: 886995
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: I1b29243bd8219e81187aa0e8c5d8f50371423126
Reviewed-on: https://chromium-review.googlesource.com/1236833
Commit-Queue: weiliangc <weiliangc@chromium.org>
Reviewed-by: weiliangc <weiliangc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592831}

AuthFailure was remembered in OnAuthFailure() by a pointer and was
freed after that leading to strange failure reason on next read.
It was introduced 5 years ago in https://crrev.com/22900017

[719:719:0918/112724.240220:ERROR:auth_status_consumer.h(95)] NOTREACHED() hit.  [Reason: info:NOTREACHED()]
[719:719:0918/112724.240293:ERROR:device_event_log_impl.cc(159)] [11:27:24.240] Login: cryptohome_authenticator.cc:725 Login failed:
[719:719:0918/112724.240371:ERROR:login_performer.cc(63)] Login failure, reason=0, error.state=0
[719:719:0918/112724.240414:ERROR:kiosk_profile_loader.cc(202)] NOTREACHED() hit.  [Reason: info:NOTREACHED()]
[719:719:0918/112724.240458:ERROR:auth_status_consumer.h(95)] NOTREACHED() hit.  [Reason: info:NOTREACHED()]
[719:719:0918/112724.240445:ERROR:kiosk_profile_loader.cc(188)] Kiosk auth failure: error=
[719:719:0918/112724.240674:ERROR:kiosk_profile_loader.cc(50)] NOTREACHED() hit.  [Reason: info:NOTREACHED()]
[719:719:0918/112724.240732:ERROR:app_launch_controller.cc(526)] Kiosk launch failed, error=4

Bug: 885346
Change-Id: I46ca3b3630aa42e25a25d9cfecb3a16e3c361b9f
Reviewed-on: https://chromium-review.googlesource.com/1236265Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592830}

ArcAppWindowLauncherController was observing the wrong aura::Env for
window creation, so it wasn't calling AttachControllerToWindowIfNeeded
to set the correct ShelfID on the window.

Bug: 887129
Test: pin Play Store icon, then tap on it
Change-Id: I2239a032962b783a50e562b822f021ef6e0a7511
Reviewed-on: https://chromium-review.googlesource.com/1235152Reviewed-by: Michael Wasserman <msw@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592829}

Both policies are deprecated and will always be false.

Remove SupervisedUsersEnabled code, for ChromeOS
Remove SupervisedUserCreationEnabled code, for Chrome
Signed-off-by: Guido Trotter <ultrotter@chromium.org>
Bug: 834488
Change-Id: Iab2fad3d396ab5d68bbd0072da742fadeb64d367
Reviewed-on: https://chromium-review.googlesource.com/1224033Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592828}

mv ntp/ContextMenuManager.java to native_page/
mv suggestions/SuggestionsNavigationDelegate.java to native_page/NativePageNavigationDelegate.java and remove suggestions-only methods
cp suggestions/SuggestionsNavigationDelegateImpl.java to native_page/NativePageNavigationDelegateImpl.java and remove suggestions-only methods
have suggestions/SuggestionsNavigationDelegate.java extend native_page/NativePageNavigationDelegateImpl to contain suggestions-only methods
update all references thereof

Bug: 867488
Change-Id: I64cb9bb6864da2a90b9358ec2a4f339d76df1cdc
Reviewed-on: https://chromium-review.googlesource.com/1232336
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592827}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I2bf66fbb151b60c3a26a2d0082ab760720a926d9
Reviewed-on: https://chromium-review.googlesource.com/1236497
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#592826}

Previously OmniboxTabSwitchButton::IsSelected() wasn't asking if
*this* result was selected, only if "the tab switch button" was
focused. This could refer to another result. This change narrows
the implementation of IsSelected() to check if this particular
result is also selected.

Bug: 886606
Change-Id: I463151848e6cefdbe3afa360d3dbc0e03d2c40ee
Reviewed-on: https://chromium-review.googlesource.com/1234033Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Kevin Bailey <krb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592825}

This CL:
  - Removes support for non-GRID tab switchers from the feature engagement egtest.
  - Simplifies tab_usage_recorder_test_util to only support the tab grid.
  - Removes non-grid support from the UKM egtest
  - Moves the TabletTabSwitcherOpenButton() helper function to chrome_matchers, out of the moribund tab_switcher/ directory.


Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I6cbcfa88f13bdad6407e56746e9e76bd9e4a5d38
Reviewed-on: https://chromium-review.googlesource.com/1233195
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592824}

Renderer initiated back/forward navigations must not be able to cancel ongoing
browser initiated navigation if they are not user initiated.

Note: 'normal' renderer initiated navigation uses the
FrameHost::BeginNavigation() path. A code similar to this patch is done
in NavigatorImpl::OnBeginNavigation().

Test:
-----

Added: NavigationBrowserTest.
 * HistoryBackInBeforeUnload
 * HistoryBackInBeforeUnloadAfterSetTimeout
 * HistoryBackCancelPendingNavigationNoUserGesture
 * HistoryBackCancelPendingNavigationUserGesture

Fixed:
 * (WPT) .../the-history-interface/traverse_the_history_2.html
 * (WPT) .../the-history-interface/traverse_the_history_3.html
 * (WPT) .../the-history-interface/traverse_the_history_4.html
 * (WPT) .../the-history-interface/traverse_the_history_5.html

Bug: 879965
Change-Id: I1a9bfaaea1ffc219e6c32f6e676b660e746c578c
Reviewed-on: https://chromium-review.googlesource.com/1209744
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592823}

These reports are only used for testing, are not web exposed, and the
flag only covers the IDL file anyway, which is unnecessary. This patch
removes that flag.

TBR: japhet@chromium.org
Change-Id: I3a1c63bbbaa2f50cec7c42217a7ce2882ae6f6c2
Reviewed-on: https://chromium-review.googlesource.com/1226077Reviewed-by: Paul Meyer <paulmeyer@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Paul Meyer <paulmeyer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592822}

These resources are used by hueristic field type prediction.

Bug: 849913
Change-Id: Iab2935bce88984c604ac87f0148910c1a4b343c2
Reviewed-on: https://chromium-review.googlesource.com/1231819
Commit-Queue: Tao Bai <michaelbai@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592821}

It causes no-over-optimization-on-uniform-array cases failing
consistently.

TBR=kbr@chromium.org

Bug: 884210
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: I5e61cdcfd793fb3a7916b9c25acca535d61771fd
Reviewed-on: https://chromium-review.googlesource.com/1235327Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592820}

Bug: 832676
Change-Id: I0fb8d4b1f0197dab0b988a52741724f63a18ee9f
Reviewed-on: https://chromium-review.googlesource.com/1236178
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592819}

- Updates _currentPage properly in response to 3-finger accessibility swipe. This will now properly read out the currently visible page if a user swipes to a different page.
- Ensures that only the currently visible page's elements can be selected in the scroll view. This resolves an issue VoiceOver was having with what page to readout and to focus on. Oftentimes the visible page was not readout or selectable.

Video: https://drive.google.com/open?id=1Q62MUlrVcNlqnFIQOfw_YiGHinTKb_45

Bug: 880079
Change-Id: I0696786292bec375af9d5326a790700000114559
Reviewed-on: https://chromium-review.googlesource.com/1221474
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592818}

Adding a DCHECK() and a null check.

Bug: 883329
Change-Id: I56efb844c7cc6788ac04e9f494608ef18e94cd78
Reviewed-on: https://chromium-review.googlesource.com/1236454Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592817}

The current implementation of DeviceReenroller uses the incorrect
callbacks to signal when an enrollment and device sync are complete.
Specifically, the ForceEnrollmentNow() and ForceSyncNow() callbacks were
used instead of the DeviceSyncClient::Observer callbacks,
OnEnrollmentFinished() and OnNewDevicesSynced().

Here, we use to the correct callbacks along with a more appropriate and
simplified retry mechanism. Namely, the complete re-enrollment
process of enrollment --> device sync --> verification is retried every
5 minutes or until success.

Note: The OnEnrollmentFinished() and OnNewDevicesSynced() callbacks
might be invoked due to enrollments or device syncs external to the
DeviceReenroller class. Regardless of how the functions are called, the
two sets of supported software features (from GCM device info and local
device metadata) are compared. If they disagree, the re-enrollment
process is triggered.

Bug: 870770
Change-Id: If33320386cd8ce5d5639082009291b935ec6e471
Tested: Manual and unit tests
Reviewed-on: https://chromium-review.googlesource.com/1228311
Commit-Queue: Josh Nohle <nohle@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592816}

In a recent cl, https://chromium-review.googlesource.com/c/chromium/src/+/1171562,
it starts to use singleton to create AcceessibillityRecorder instance.
This causes a problem in crbug.com/883136, that because the dtor will
never be called, windowns event will still be caught and processed during
destuction period, which may randomly crash due to race condition.

This cl is to partially revert the changes to stop listening correctly
at destruction.

Bug: 883136
Change-Id: I1bd8d3e00b23590c222652c15632e33b4e3667e9
Reviewed-on: https://chromium-review.googlesource.com/1234853
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592815}

The embedder has been migrated to Custom Elements V1, so there is no
longer any need for Custom Elements V0 to register elements with
non-standard names.

Bug: 867831
Change-Id: I96a48fcf8560e08c8286081b844be93a3a630159
Reviewed-on: https://chromium-review.googlesource.com/1220036Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592814}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a6fb5c9cdd1b..fd2e62420dba


Created with:
  gclient setdep -r src-internal@fd2e62420dba

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.


TBR=mmoss@chromium.org

Change-Id: Ie7d505fac21293dd4d8d80608cb28e8755dc9607
Reviewed-on: https://chromium-review.googlesource.com/1235843Reviewed-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@{#592813}

https://chromium.googlesource.com/catapult.git/+log/985f6fe58181..5e97145328bd


git log 985f6fe58181..5e97145328bd --date=short --no-merges --format='%ad %ae %s'
2018-09-20 sadrul@chromium.org trace-viewer: Allow filtering processes.


Created with:
  gclient setdep -r src/third_party/catapult@5e97145328bd

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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=sullivan@chromium.org

Change-Id: I53f0902ab938016d3e3c60e6638a3efbd0abf7cf
Reviewed-on: https://chromium-review.googlesource.com/1235842Reviewed-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@{#592812}

Moves functionality from content/renderer/fileapi to
blink/renderer/modules/filesystem:

- Moves most functionality in content::FileSystemDispatcher and
  content::WebFileSystemImpl into blink::FileSystemDispatcher
- Moves all functionality in content::WebFileWriterBase to
  blink::FileWriterBase
- Moves all functionality in content::WebFileWriterImpl to
  blink::FileWriter and blink::FileWriterSync
- Move web_file_writer_base_test.cc to blink
- Removes WebFileWriter, WebFileWriterClient, WebFileSystemCallbacks,
  WebFileError, WebFileInfo, WebFileSystemEntry
- Makes AsyncFileSystemCallbacks and FileSystemCallbacks use
  base::File::Error directly instead of using blink::FileError.

Bug: 787281
Change-Id: Iff0ca3e9fe20d0586709c5efbce4cd1cc79c1419
Reviewed-on: https://chromium-review.googlesource.com/1195098Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592811}

I've got an email suggesting to add a Monorail component for benchmark
startup.mobile.

I think "Speed>Metrics>SystemHealthRegressions" is the component that
best matches the bug target for startup.mobile. The description for this
component says:
    "Any performance regressions detected in the lab, in production or
     extraneous to automated tool that need a human step .."

Bug: None
Change-Id: Idf857073114886f00c4772a02643d402997ee9e1
Reviewed-on: https://chromium-review.googlesource.com/1233741Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592810}

This path has been disabled since crrev.com/c/1024703, so remove dead
code.

Bug: 882513
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I2b6e076bd97b62464c3c1d9508827f7ac4be4561
Reviewed-on: https://chromium-review.googlesource.com/1234238
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592809}

URLFetcher will stop working with advent of Network Service, and
SimpleURLLoader is the replacement API for most clients.
This CL migrates URLDownloader and the respective unittests away
from URLFetcher.

BUG=773295

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I8abfd9c9d9e66757c555479fe6a153e3dc08b9c5
Reviewed-on: https://chromium-review.googlesource.com/1234635Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#592808}

AssemblePasswordForm inside
components/password_manager/core/browser/form_parsing/form_parser.cc
currently gets a pointer to SignificantFields and checks it for being
null. However, it is never called with the pointer being null.

To clarify the code, this CL changes the AssemblePasswordForm
signature to expect a reference instead.

Bug: 883633
Change-Id: I2a81350836074ca60e925a2a0bd28b5fa0169281
Reviewed-on: https://chromium-review.googlesource.com/1235582Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592807}

Bug: 809610
Change-Id: Ib9403a5a18424fe37a7a85ab9c3b6ff90e59b614
Reviewed-on: https://chromium-review.googlesource.com/1235719Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592806}

Bug: 766206
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ifb5996a5491bde08885517ad56a539d73cf60260
Reviewed-on: https://chromium-review.googlesource.com/1235223
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592805}

This CL modifies SyncAndServicesPreferences to check off and disable
'Activity and interactions' checkbox if history sync is turned off. The
same restriction is already implemented for Autofill and Payments
checkboxes, so this CL just uses the existing pattern.

Bug: 885356
Change-Id: I40913c0c71dd1b8ad399c81b0031e623c7d74e6d
Reviewed-on: https://chromium-review.googlesource.com/1236273Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592804}

Simplify logic and code by getting rid of the secondary priority queue that was tracking the times at which ProcessRipeTasks() was scheduled, and replacing it by a simple boolean flag for each delayed task.

See https://chromium-review.googlesource.com/c/chromium/src/+/1196844/13/base/task/task_scheduler/delayed_task_manager.h#89

Change-Id: I1ea6312183eaf8fc4ce45c5d668e4e5a13506e11
Reviewed-on: https://chromium-review.googlesource.com/1230694
Commit-Queue: Alexandre Frechette <frechette@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592803}

Roll src/third_party/SPIRV-Tools/src/ 0cd3e599a..6e2dab2ff (3 commits)

$ git log 0cd3e599a..6e2dab2ff --date=short --no-merges --format='%ad %ae %s'
2018-09-19 chaoc Add support for Nvidia Turing extensions
2018-09-19 stevenperron Add unrolling to the legalization passes (#1903)
2018-09-17 jaebaek Specified clang-format version in README.md

Created with:
  roll-dep src/third_party/SPIRV-Tools/src

Roll src/third_party/spirv-headers/src/ dcf23bdab..d5b2e1255 (2 commits)

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Headers.git/+log/dcf23bdabacc..d5b2e1255f70

$ git log dcf23bdab..d5b2e1255 --date=short --no-merges --format='%ad %ae %s'
2018-09-19 cepheus Fix D -> d typo in previous commit.
2018-09-19 cepheus Add enumerants for six Nvidia extensions:

Created with:
  roll-dep src/third_party/spirv-headers/src

TBR=dneto@chromium.org

Change-Id: I024cb5917c5b0aaf61110a534ffa7d7b6664ab15
Reviewed-on: https://chromium-review.googlesource.com/1236373Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: dsinclair <dsinclair@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592802}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/79023740..08b9e376

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I0857369ad18bd563030d6f83d3ede03cd12b6743
Reviewed-on: https://chromium-review.googlesource.com/1235896Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#592801}

Make ForwardingAudioStreamFactory hosting the source streams to be
aware that it's being captured by a loopback sinks. Notify loopback sinks
when the source ForwardingAudioStreamFactory (i.e. WebContents whch owns it)
is being destroyed.

Bug: 866440,852880,866442
Change-Id: I4a46952cafd378f87ceb7da4a1c1ce27341babd9
Reviewed-on: https://chromium-review.googlesource.com/1221318
Commit-Queue: Max Morin <maxmorin@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592800}

This CL uses ScopedBlockingCall to mark blocking calls in /chrome/browser/media.

This CL was created by replacing calls to AssertBlockingAllowed()
with instantiations of ScopedBlockingCall(MAY_BLOCK).
I kindly ask the reviewer to make sure of the following:
  - ScopedBlockingCall is instantiated in a scope with minimal CPU usage.
    If this is not the case, ScopedBlockingCall should be instantiated
    closer to the blocking call. See scoped_blocking_call.h for more
    info. Please let me know when/where the blocking call happens if this needs
    to be changed.
  - Parameter |blocking_type| matches expectation (MAY_BLOCK/WILL_BLOCK). See
    BlockingType for more info. While I assumed MAY_BLOCK by default, that might
    not be the best fit if we know that this callsite is guaranteed to block.
  - The ScopedBlockingCall's scope covers the entirety of the blocking operation
    previously asserted against by the AssertBlockingAllowed().

This CL was uploaded by git cl split.

R=chcunningham@chromium.org

TBR=chcunningham@chromium.org

Bug: 874080
Change-Id: If0029c7a63eb0cc35a18dbcec7c21cbdaeeaf156
Reviewed-on: https://chromium-review.googlesource.com/1191193
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Yuchen Liu <yucliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592799}

These two files are unused after
https://chromium-review.googlesource.com/c/chromium/src/+/1234473

Bug: 832676
Change-Id: I216ee64cda26ba618a8b89bd8dc216aef6f567f5
Reviewed-on: https://chromium-review.googlesource.com/1236176Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592798}

https://chromium.googlesource.com/external/github.com/google/re2.git/+log/4c916c947ab7..bfe29206c269

$ git log 4c916c947..bfe29206c --date=short --no-merges --format='%ad %ae %s'
2018-09-19 junyer Crudely limit the use of . when fuzzing.

Created with:
  roll-dep src/third_party/re2/src

Bug: 884457
Change-Id: Id978d2f46c8c0fdf2017d4c3cba78b75797fd17a
Reviewed-on: https://chromium-review.googlesource.com/1235336Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592797}

Replace the remaining references to BrowserThread::PostTask with the
base::PostTaskWithTraits API.

These locations weren't covered by the global replacement patch as they
were either added recently or ignored by the script.

TBR=lazyboy@chromium.org

Bug: 878356
Change-Id: Id199777ae6bcb30ebb03b767f9cd8c6f981c6ac4
Reviewed-on: https://chromium-review.googlesource.com/1235727
Commit-Queue: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Alex Clarke <alexclarke@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592796}

This updates the closures and callbacks to use the "Once"
paradigm as per the style guide/presubmission warnings.
All of the instances were switched over to "Once".

Bug: 884057
Change-Id: I93a63e79c6e142051a80eea433f29239a1f3b28d
Reviewed-on: https://chromium-review.googlesource.com/1234217
Commit-Queue: Eric Robinson <ericrobinson@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592795}

ProfileOAuth2TokenService has a corner case wherein during startup,
it can fire token removal notifications for accounts for which it has
never previously filed a token available notification. IdentityManager
currently swallows such notifications. However, as we streamline
IdentityManager to be just a straight pass-through to its backing
classes (crbug.com/883722), IdentityManager will no longer be able
to detect this case (because it won't be maintaining any cached info
from the token available notifications).

This CL makes the behavioral change of having IdentityManager always
pass on token removal notifications from ProfileOAuth2TokenService.
The behavioral impact is that consumers of
IdentityManager::Observer::OnRefreshTokenRemovedForAccount() will now
see a removal notification in the corner case described above. However,
all such consumers were previously consumers of
ProfileOAuth2TokenService::Observer::OnRefreshTokenRevoked() before
their conversion and hence were previously seeing the removal
notification in this corner case. Thus, the behavioral change does
not seem to have a concrete impact on consumers one way or the other.

Bug: 883722
Change-Id: I131ad8dbe12d73772845fd2eb565cd3477779c36
Reviewed-on: https://chromium-review.googlesource.com/1225878Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592794}