- 26 Apr, 2019 40 commits
-
-
Juan Antonio Navarro Perez authored
Data is now coming from new bot in the main waterfall. Also take the chance to fix typo in cloud storage bucket name. Bug: 943601 Change-Id: Ia825557783afe878db0ad95637c7bf57ee2d09b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584309 Auto-Submit: Juan Antonio Navarro Pérez <perezju@chromium.org> Reviewed-by:
Simon Hatch <simonhatch@chromium.org> Commit-Queue: Simon Hatch <simonhatch@chromium.org> Cr-Commit-Position: refs/heads/master@{#654455}
-
Jan Krcal authored
This CL fixes flaky tests by using a more careful initial setup procedure that avoids race conditions. Bug: 956043 Change-Id: I606f198c6783a450086cdea166875408bdf1fc39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584274 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#654454}
-
Daniel Bratell authored
chrome/browser/previews have two distinct (but similar) RemoveStaleEntries functions and in some extreme jumbo builds they compile in the same translation unit and clash. This CL renames them RemoveStaleBlacklistEntries and RemoveStaleOfflinePageEntries. Bug: 914577 Change-Id: I69a837393d0586194bcd85f66eadfe85522418e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584261 Commit-Queue: Robert Ogden <robertogden@chromium.org> Auto-Submit: Daniel Bratell <bratell@opera.com> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#654453}
-
Lily Chen authored
This CL implements the interface between NetworkErrorLoggingServiceImpl and its PersistentNELStore. If a store is provided upon construction, The NetworkErrorLoggingService will attempt to load all NEL policies from the store on the first call to OnHeader(), OnRequest(), QueueSignedExchangeReport(), RemoveBrowsingData(), or RemoveAllBrowsingData(). Until the store notifies us that it is done loading, calls to those public methods will be queued in a backlog to be run in order upon completion of loading. Any changes to the NEL policies stored in memory will be reflected in the PersistentNELStore. Bug: 895821 Change-Id: Ib9a18a2b6c73641ee0a3d2f7b119b4c710c4db5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555242 Commit-Queue: Lily Chen <chlily@chromium.org> Reviewed-by:
Eric Orth <ericorth@chromium.org> Reviewed-by:
Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#654452}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/152ac9be2f84..d3aeecd01069 git log 152ac9be2f84..d3aeecd01069 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 michaelludwig@google.com Visualize geometry domains in degenerate quad sample Created with: gclient setdep -r src/third_party/skia@d3aeecd01069 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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=mtklein@chromium.org Change-Id: I6ca0842544d91aabda37fc32df2a094e94eba89a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585919Reviewed-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@{#654451}
-
Jan Krcal authored
This CL fixes a few flaky tests for theme sync by using a more careful process for initial sync setup. Bug: 956043 Change-Id: Id0d92c87af973fc5ba62e3e4dee29fcf5d1fdf2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583706Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#654450}
-
Liquan(Max) Gu authored
The text side of FCP++ should update the candidate when any node is removed in the same frame, in the same style as the image side. Before, we didn't update candidate on node removal unless the node is the last detached node. We shouldn't special case this. Instead, everytime a node is removed we should update the candidate. Bug: 948119 Change-Id: Ia4075be5148168c47222f31d775bfa07436c0d23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1579248 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#654449}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/42fa30fdac9a..eb37b1394300 git log 42fa30fdac9a..eb37b1394300 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 peah@webrtc.org Add peah to more audio watchlists 2019-04-26 philipel@webrtc.org Use CodecBufferUsage to determine dependencies. 2019-04-26 solenberg@webrtc.org Reduce watchlist spam for myself. 2019-04-26 peah@webrtc.org Allow setting the AGC2 fixed gain during runtime 2019-04-26 henrik.lundin@webrtc.org NetEq: Create an audio interruption metric Created with: gclient setdep -r src/third_party/webrtc@eb37b1394300 The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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. BUG=chromium:none,chromium:none TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I5195ff21c68039859537c4395d55f90becbf9dd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585816Reviewed-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@{#654448}
-
Oskar Sundbom authored
Speculative fix for what looks like a race during CoreAudio initialization. The device enumerator created to ensure for CoreAudio availability is leaked rather than destroyed immediately after construction. Bug: 955434 Change-Id: Ifa70350691448ec6ba57c9eb2b93106aa8edf65b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584276Reviewed-by:
Olga Sharonova <olka@chromium.org> Commit-Queue: Oskar Sundbom <ossu@chromium.org> Cr-Commit-Position: refs/heads/master@{#654447}
-
Daniel Cheng authored
Bug: 841899 Change-Id: I5e66901262c7ccfe5bbedd67203572c55d53b881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584591 Auto-Submit: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/master@{#654446}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/809c46b7808b..419c9cd57073 Created with: gclient setdep -r src-internal@419c9cd57073 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=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org Change-Id: Idf30619edeed4f6848ae4cd01303d19e5415b13a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585817Reviewed-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@{#654445}
-
Liquan(Max) Gu authored
In this CL we explicitly exclude body from being captured as a background image. Before, we assumed that the background image would automatically be transferred to the layout view. But that's not the case in some examples, as found by the attached bug. Bug: 952828 Change-Id: I8f1c97e924ae14e61ac39d7d86af801a93f2863b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1579253 Auto-Submit: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#654444}
-
Michael Lippautz authored
- Slots and references are on-heap these days as Persistent heap collections are gone for quite some time now. Remove off-heap logic and add CHECKs for on-heap at the very beginning. - DCHECK->CHECK until compaction has been stabilized for incremental marking. - Add liveness checks for slot and reference. - Inline AddInteriorFixup helper method that cannot be called stand-alone. Bug: 918064 Change-Id: Ia343f67b3a715c954bccbf3bf939f39875b5e22e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584302 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#654443}
-
Abhijeet Kandalkar authored
Bug: 891908 Change-Id: I0c2c3add660f0ae4373bca1844d2730ba184b5e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1580989 Commit-Queue: Abhijeet Kandalkar <abhijeet@igalia.com> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#654442}
-
Bruno Santos authored
Following advice in https://crrev.com/c/1570426 Bug: 927809 Change-Id: I377ef29160228abc1a4242156974c8de926d9fa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584874Reviewed-by:
Lucas Tenório <ltenorio@chromium.org> Commit-Queue: Bruno Santos <brunoad@chromium.org> Cr-Commit-Position: refs/heads/master@{#654441}
-
Sahel Sharify authored
This cl adds IconSizeCalculator helper class so that payment icon related files uses this class for the ideal icon size. Bug: 879741 Change-Id: I0f3a912c98e7c4d605c2b8e88203cf4ce5573278 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574687Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#654440}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: Ib1d75e52f326a6e23cd42a5eee812fb02ef7579f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585818Reviewed-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@{#654439}
-
Dave Tapuska authored
There already was a pass expectation for the non-worker case but it appears we need one for the worker case in order to land the V8 change. BUG=948678 Change-Id: I6c670b52e93e4de4449835b31bc4d336f58140b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585814Reviewed-by:
Mustaq Ahmed <mustaq@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#654438}
-
chromium-autoroll authored
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;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: I2fca490a57e7c7dd2a45372afa05e5600f48e3c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585812Reviewed-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@{#654437}
-
Miyoung Shin authored
This is a followup CL of https://crrev.com/c/1575315. This CL uses bit_cast<float> to convert FloatSize's width/height for Hash similar to WTF::FloatHash and WTF::FloatHashTraits. Bug: 952716 Change-Id: Ibafa38c9f1481472066c5a556297ee2d630e1e46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585286Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Miyoung Shin <myid.shin@igalia.com> Cr-Commit-Position: refs/heads/master@{#654436}
-
Dan Zhang authored
R=rch@chromium.org Change-Id: I345efbb9d5ba4ba21eb50433b6d579307dffbb7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568848 Commit-Queue: Dan Zhang <danzh@chromium.org> Reviewed-by:
Ryan Hamilton <rch@chromium.org> Cr-Commit-Position: refs/heads/master@{#654435}
-
Mike Reed authored
Also, color values in skia are now explicitly floats, not SkScalar. Bug: skia:4872 Bug: skia:9012 Change-Id: Ia4fc7c20048d6d273c59f852741d9f7fd71d8d46 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582771 Commit-Queue: Mike Reed <reed@google.com> Reviewed-by:
Eric Karl <ericrk@chromium.org> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#654434}
-
manuk authored
Document responses contain both an 'originalUrl' and a 'url' field. The 'url' field contains some extraneous query params that can hinder deduping. When document suggestions are initially constructed in `DocumentProvider::ParseDocumentSearchResults`, we set `stripped_url`, used for deduping, using the 'originalUrl' response field. When actually deduping suggestions later in `AutocompleteResult::SortAndCull`, we overwrite the `stripped_url` field with a new value computed from 'url'. This CL avoids overwriting `stripped_url` if it's already set during deduping. This is necessary for document suggestion deduping, but also non-harmful for other providers as the computed stripped_destination_url does not change during a match's lifecycle. Bug: 888093 Change-Id: I72ea697a661ffab496d385edead063caba366573 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1574781 Commit-Queue: manuk hovanesian <manukh@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#654433}
-
Armando Miraglia authored
Some tests in webrtc_image_capture_browsertest.cc are still defined as MAYBE_* but they are currently always enabled. This CL is renaming the tests and dropping the MAYBE_* macros. BUG=793859 Change-Id: I3e45742b17da920138df872ecb8895dcc9ebcaa7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583733Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Armando Miraglia <armax@chromium.org> Cr-Commit-Position: refs/heads/master@{#654432}
-
Armando Miraglia authored
From the review in http://crrev.com/c/1584271 it was suggested that I should be added to the OWNERS file of the WPT tests for mediacapture-streams for communication purposes. This CL adds the armax@chromium.org address as owner. BUG=None Change-Id: Ic2fedd21414ac25e28ffbfbe50c707d045e76433 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584308Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Armando Miraglia <armax@chromium.org> Cr-Commit-Position: refs/heads/master@{#654431}
-
Peter Beverloo authored
Change-Id: I6a3f622284c720130a91ee508bffd0d44d08848a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583707 Commit-Queue: Peter Beverloo <peter@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Auto-Submit: Peter Beverloo <peter@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#654430}
-
Carlos Caballero authored
This check is adding no value. Enabling BEST_EFFORT queues multiple times in not bad per se. Moreover this does not play nicely with tests as some will run the initialization code in BrowserMainLoop::InitializeMainThread that posts a AfterStartupTask to enable the queues and also call SetBrowserStartupIsCompleteForTesting (to enable AfterStartupTasks). This leads to EnableBestEffortQueues() being called twice and thus a CHECK fail. We are in the process of refactoring all this code and eventually AfterStartupTaskUtils will go away, so it makes little sense to come up with a complicated workaround for this isse. Removing the check for now should be enough and in the future we might consider adding some sort of check back (it probably makes more sense to check that we do not signal BrowserStartupCompleted multiple times) Bug: 863341 Change-Id: I29acaccc281efe764579d968e38a06f9dcbe54dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584502Reviewed-by:
Alex Clarke <alexclarke@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Carlos Caballero <carlscab@google.com> Cr-Commit-Position: refs/heads/master@{#654429}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/fab73b886ed6..809c46b7808b Created with: gclient setdep -r src-internal@809c46b7808b 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=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org Change-Id: Ifc8f5e6e944e01829d5d69f09db1d038552621f3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585810Reviewed-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@{#654428}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/5ee4ec84de3c..6e345f4e28d3 git log 5ee4ec84de3c..6e345f4e28d3 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 nuskos@google.com Prevent the IPC layer from being included in builds it can't compile on. 2019-04-26 treehugger-gerrit@google.com Merge "trace_processor: Deal correctly with zero-duration scoped slices" 2019-04-25 gijosh@google.com Merge "Hardcode estimated size of local_t for X86 Android builds" 2019-04-25 treehugger-gerrit@google.com Merge "Allow chromium to build the IPC layer." 2019-04-25 hjd@google.com Merge "perfetto-ui: Fix thread state" 2019-04-25 hjd@google.com Merge "perfetto-ui: Fix crash in logs controller" 2019-04-25 bhamrick@google.com Merge "Add parser for Fuchsia traces" Created with: gclient setdep -r src/third_party/perfetto@6e345f4e28d3 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: I6f9b901e36296a064a67038a1b6fcf98f5f878bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585809Reviewed-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@{#654427}
-
Richard Knoll authored
We delete |service_proxy_| on the UI thread in Shutdown but access it from the |task_runner_| which leads to an ASAN error. Instead of that just set a flag and invalidate weak pointers to |service_proxy_|. This ties the lifetime of |service_proxy_| to its owner so we can skip null checks for it. Bug: 905352 Change-Id: I4aa105dac710496c2e988549fa4b5b4778f6d5b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570027Reviewed-by:
Peter Beverloo <peter@chromium.org> Commit-Queue: Richard Knoll <knollr@chromium.org> Cr-Commit-Position: refs/heads/master@{#654426}
-
Aditya Keerthi authored
The InvalidateFontCacheOnPurge experiment shows that font cache invalidation negatively impacts tab switch times. Furthermore, clearing the cache was shown to have no significant effect on memory. Consequently, we should not invalidate the font cache when a memory purge is triggered in a renderer. Bug: 926186, 939543 Change-Id: I315352f2f463f1ae1c8bca3bf649afbd556c2c8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584882Reviewed-by:
François Doray <fdoray@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Aditya Keerthi <adityakeerthi@google.com> Cr-Commit-Position: refs/heads/master@{#654425}
-
Jan Krcal authored
This CL fixes the test flaky on chromeos-rel by introducing additional waiting. Bug: 956043 Change-Id: Ia722f2634bbf17e037bfde02f5ec53a2500f2fb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584505 Commit-Queue: Jan Krcal <jkrcal@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Auto-Submit: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#654424}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/84650dc1..c6fbb279 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I8ddf3f03da0f819225f428032789c46ee1d362a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585808Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#654423}
-
Anders Hartvoll Ruud authored
This reverts commit 65046b8f. Reason for revert: broke Android CFI. Original change's description: > Update Linux Seccomp syscall restrictions to EPERM posix_spawn/vfork > > Glibc's system() function switched to using posix_spawn, which uses > CLONE_VFORK. Pepperflash includes a sandbox debugging check which > relies on us EPERM-ing process creation like this, rather than crashing > the process with SIGSYS. > > So whitelist clone() calls, like posix_spawn, that include the flags > CLONE_VFORK and CLONE_VM. > > Bug: 949312 > Change-Id: I3f4b90114b2fc1d9929e3c0a85bbe8f10def3c20 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1568086 > Commit-Queue: Robert Sesek <rsesek@chromium.org> > Reviewed-by: Robert Sesek <rsesek@chromium.org> > Cr-Commit-Position: refs/heads/master@{#653590} TBR=jorgelo@chromium.org,thestig@chromium.org,tsepez@chromium.org,rsesek@chromium.org,mpdenton@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 949312 Change-Id: I4628a3883a4aa5ac9f14c815380c2e52b0469715 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584305Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#654422}
-
Jan Krcal authored
This CL fixes a few integration tests using custom passphrases by introducing additional waiting. Bug: 956012, 956043 Change-Id: Ie28e9f99c71db30c1df5067991c8b6867f36a9e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585880Reviewed-by:
Mohamed Amir Yosef <mamir@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#654421}
-
Jan Krcal authored
This CL fixes the test UnifiedConsentBrowserTest.SettingsOptInTakeOverServicePrefChanges that has been recently disabled. Bug: 954167, 956043 Change-Id: Ibcbd5119afb1e91dce22d377b10a1414eac8420a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584273Reviewed-by:
Thomas Tangl <tangltom@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#654420}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/f82158fb7fdc..152ac9be2f84 git log f82158fb7fdc..152ac9be2f84 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 halcanary@google.com Fix MoltemVk Bots Created with: gclient setdep -r src/third_party/skia@152ac9be2f84 The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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=mtklein@chromium.org Change-Id: Ia9e0f27cb14d0022f28246062e2ddec727c5ad34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585807Reviewed-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@{#654419}
-
Anders Hartvoll Ruud authored
BUG=956990 TBR=dmazzoni@chromium.org Change-Id: I0b01b937951938b1116d22e250b8cc505f57754c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583898Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#654418}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/be4f95d279c6..fab73b886ed6 Created with: gclient setdep -r src-internal@fab73b886ed6 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=andruud@chromium.org,alexmos@chromium.org,horo@chromium.org,adithyas@chromium.org Change-Id: I7c1452d942832b053a4e80f413db7207fc61ce94 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585806Reviewed-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@{#654417}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/8e97b4c8a512..15d4c2e63b72 git log 8e97b4c8a512..15d4c2e63b72 --date=short --no-merges --format='%ad %ae %s' 2019-04-26 jiawei.shao@intel.com Emulate store and multisample resolve on Metal Created with: gclient setdep -r src/third_party/dawn@15d4c2e63b72 The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel TBR=cwallez@chromium.org Change-Id: Ibaf6e11999d8a9920d75d94d395dd82ef40dd8a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585805Reviewed-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@{#654416}
-