GitLab

This pulls in the following Native Client changes:

r13760: (mseaborn) untrusted.gypi: Factor out duplicated "--gomadir" option
r13761: (mseaborn) Fix mmap() with length > 0xffff0000 to behave consistently on 32/64-bit
r13762: (teravest) Support file path metadata for the main nexe.
r13763: (teravest) Add CreateNaClDescWithFilePathMetadata fn.
r13764: (dschuff) Switch PNaCl lib, include, and translator directories for new layout
r13765: (dschuff) Pass naclsdk_validate=0 to scons runs run by main waterfall bots
r13768: (dbrazdil) Allowed decrementing program break with sbrk() in MinSFI
r13769: (dyen) Added tests for rename functions in irt_ext.
r13770: (dyen) Added tests for unlink functions irt_ext.
r13771: (dschuff) Update revision for PNaCl r13753->r13769
r13772: (dyen) Added tests for fsync/fdatasync functions in irt_ext.
r13773: (petarj) PNaCl: Update libcxx revision in pnacl/COMPONENT_REVISIONS
r13774: (dyen) Added tests for file truncation functions in irt_ext.
r13775: (sehr) Add Nick Bray and Shyam as owners of the validator
r13776: (jvoung) Remember to va_end in callingconv test.
r13777: (shyamsundarr) a script to generate a trie from our DFA.
r13778: (shyamsundarr) updated version of mseaborn@chromium's old trie code. We will generate
r13779: (dschuff) Allow build of host tools with system compiler
r13780: (dyen) Added support for supplying futex calls under irt_ext.
r13781: (dschuff) Remove archived_frontend test and use gcc build for FYI bots
r13782: (dschuff) Clang and binutils for direct to nacl x86_64
r13783: (dschuff) Change prep_nacl_sdk header locations for PNaCl to match new layout
r13784: (dschuff) Revert r13723, r13730, r13744
r13785: (dschuff) Revert "untrusted.gypi: Factor out duplicated "--gomadir" option"

This also adjusts the SDK header copying script to put the libnacl
headers in the new location for PNaCl.

BUG=none
TEST=browser_tests and nacl_integration
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_rel_precise32,linux_nacl_sdk,linux_chromium_dbg

Review URL: https://codereview.chromium.org/597393003

Cr-Commit-Position: refs/heads/master@{#296781}

As a part of making Android CompositorImpl use cc's scheduler and not
post its own composite calls manually, cc needs to be able to handle
asynchronous output surface creation.

This change modifies CreateOutputSurface to instead be
RequestNewOutputSurface, which the LayerTreeHostClient must respond to
and call SetOutputSurface on the host with the new output surface once
it is ready.

Because the LayerTreeHostClient must now talk to the host as a part of
output surface creation, a bunch of unit test code needed to be
refactored to handle this.

BUG=none

Review URL: https://codereview.chromium.org/348093004

Cr-Commit-Position: refs/heads/master@{#296780}

We should not end up in the default implementation and want to track if this happens.

* Add new media stream result, "not supported".
* Add an error log in RenderFrameHostDelegate and WebContentsDelegate default implementations of the above functions and in Request... also use the new result.

BUG=416233
NOTRY=true

Review URL: https://codereview.chromium.org/584383002

Cr-Commit-Position: refs/heads/master@{#296779}

Caching these saves time recreating and remapping them.

Review URL: https://codereview.chromium.org/600953003

Cr-Commit-Position: refs/heads/master@{#296778}

BUG=416561

Review URL: https://codereview.chromium.org/603023002

Cr-Commit-Position: refs/heads/master@{#296777}

BUG=413772

NOTRY=true

Review URL: https://codereview.chromium.org/580293002

Cr-Commit-Position: refs/heads/master@{#296776}

BUG=417660

Review URL: https://codereview.chromium.org/601303002

Cr-Commit-Position: refs/heads/master@{#296775}

Thanks to swarming we can do with just one builder,
linux_chromium_asan_rel.

BUG=404694, 387743
R=jam@chromium.org

Review URL: https://codereview.chromium.org/599313002

Cr-Commit-Position: refs/heads/master@{#296774}

BUG=314889

Review URL: https://codereview.chromium.org/595413002

Cr-Commit-Position: refs/heads/master@{#296773}

R=brettw@chromium.org

Review URL: https://codereview.chromium.org/587153003

Cr-Commit-Position: refs/heads/master@{#296772}

Previously it was possible to run into situations where CMake would fail,
write a partial CMakeCache.txt, and on the next run of update.sh, we would
think the build was already configured and skip the CMake step.

This patch removes that problem by always clearing the cache and forcing
a full re-run of CMake. This also has the benefit that if the path to the
compiler or a compiler flag changes, the build will get updated.

Note that doing a full re-run of CMake doesn't mean doing a full re-build.

Also, we should only be setting MACOSX_DEPLOYMENT_TARGET when doing bootstrap
builds. This patch fixes that too.

BUG=415670

Review URL: https://codereview.chromium.org/603943003

Cr-Commit-Position: refs/heads/master@{#296771}

Passing --trace-to-file on the command line will trace a default set of
categories to a default trace file name (trace.json).
--trace-to-file=categories --trace-to-file-name=somefile.json allow for
more configuration.

BUG=none

Review URL: https://codereview.chromium.org/542893002

Cr-Commit-Position: refs/heads/master@{#296770}

This matches the NSS port's behavior. If an unknown error within ERR_LIB_SSL,
map to ERR_SSL_PROTOCOL_ERROR. Otherwise, map to ERR_FAILED. The OpenSSL port
actually inverted this for some reason.

(This doesn't fix #417134 but maps it to a more appropriate error.)

BUG=417134

Review URL: https://codereview.chromium.org/598043002

Cr-Commit-Position: refs/heads/master@{#296769}

Enable WebGL on Mali-400 GPUs that support the EXT_robustness extension
but do *not* send context reset notifications. The reason we can do
this is that virtualized contexts are not used on these devices, so
badly behaving WebGL shaders do not affect other GL contexts. This means
that the user can close or reload the WebGL tab and other tabs in the
browser remain responsive.

BUG=288731,416690
TEST=https://www.khronos.org/registry/webgl/conformance-suites/1.0.1/extra/slow-shader-example.html on a Galaxy Tab 3

Review URL: https://codereview.chromium.org/24037006

Cr-Commit-Position: refs/heads/master@{#296768}

BUG=416983

Review URL: https://codereview.chromium.org/606763002

Cr-Commit-Position: refs/heads/master@{#296767}

This updates the SDK forward declarations and adds dark resources.

R=rsesek@chromium.org
BUG=402787

Review URL: https://codereview.chromium.org/564953002

Cr-Commit-Position: refs/heads/master@{#296766}

The look of the focus ring now closely matches the one drawn by the
ChromeVox content script using CSS, and it smoothly animates from one
location to the next.

BUG=314889

Review URL: https://codereview.chromium.org/602813003

Cr-Commit-Position: refs/heads/master@{#296765}

This change was verified using depot_tools/watchlists.py

BUG=NONE

Review URL: https://codereview.chromium.org/604063002

Cr-Commit-Position: refs/heads/master@{#296764}

Revert of Remove unneeded Friend from chrome_metrics_service_accessor (patchset #1 id:20001 of https://codereview.chromium.org/601243002/)

Reason for revert:
We need to bring this back since the usage of it is coming back in an upcoming patch.

Sorry about that...

BYE
MAD

Original issue's description:
> Remove unneeded Friend from chrome_metrics_service_accessor
>
> BUG=
>
> Committed: https://crrev.com/ca032c3aed93e5afd7c32da76147f36a72dc4341
> Cr-Commit-Position: refs/heads/master@{#296722}

TBR=asvitkine@chromium.org,csharp@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=

Review URL: https://codereview.chromium.org/603173003

Cr-Commit-Position: refs/heads/master@{#296763}

R=lcwu@chromium.org
BUG=None

Review URL: https://codereview.chromium.org/604933002

Cr-Commit-Position: refs/heads/master@{#296762}

Review URL: https://codereview.chromium.org/598053003

Cr-Commit-Position: refs/heads/master@{#296761}

We still need to clean up style violations and add i18n to all of these.

BUG=416983
R=plundblad@chromium.org

Review URL: https://codereview.chromium.org/593293002

Cr-Commit-Position: refs/heads/master@{#296760}

BUG=416722
R=scottbyer@chromium.org

Review URL: https://codereview.chromium.org/605563002

Cr-Commit-Position: refs/heads/master@{#296759}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/2540f38..7214955

TBR=ager@chromium.org,zmo@chromium.org

Review URL: https://codereview.chromium.org/605783002

Cr-Commit-Position: refs/heads/master@{#296758}

Previously we were relying on the Browser to update to the showing state, but
this would sometimes lead to the top controls to flicker while navigating since
the compositor initialized them to hidden.

BUG=416944

Review URL: https://codereview.chromium.org/597393002

Cr-Commit-Position: refs/heads/master@{#296757}

BUG=409100
R=tengs@chromium.org

Review URL: https://codereview.chromium.org/597803002

Cr-Commit-Position: refs/heads/master@{#296756}

Add more discussion links.

BUG=none
R=jamesr@chromium.org

Review URL: https://codereview.chromium.org/604833003

Cr-Commit-Position: refs/heads/master@{#296755}

BUG=416707
TBR=joaodasilva

Review URL: https://codereview.chromium.org/601133002

Cr-Commit-Position: refs/heads/master@{#296754}

BUG=415372

Review URL: https://codereview.chromium.org/596843002

Cr-Commit-Position: refs/heads/master@{#296753}

The underlying ki_init functions were returning
their success but for some reason nacl_io_init was
ignoring this and returning void.

Review URL: https://codereview.chromium.org/598223004

Cr-Commit-Position: refs/heads/master@{#296752}

Not exact revert of https://codereview.chromium.org/488853002

BUG=374321,416396

Review URL: https://codereview.chromium.org/597933002

Cr-Commit-Position: refs/heads/master@{#296751}

Add a drainData(dataPipeHandle) utility function to the Mojo JS core module.

The drainData() function asynchronously reads from the data pipe until the remote handle is closed or an error occurs. A Promise is returned whose settled value is an object like this: {result: core.RESULT_OK, buffer: dataArrayBuffer}. If the read failed, then the result will be the actual error code and the buffer will contain whatever was read before the error occurred. The drainData dataPipeHandle argument is closed automatically.

BUG=414338

Review URL: https://codereview.chromium.org/577733002

Cr-Commit-Position: refs/heads/master@{#296750}

is the address.

This code is not hooked up into QUIC code yet. Will submit that in
the next CL.

R=rch@chromium.org

Review URL: https://codereview.chromium.org/605563003

Cr-Commit-Position: refs/heads/master@{#296749}

Pass the system url request context getter to the cast service so that it can be used by various system components (e.g. cast receiver).

BUG=None

Review URL: https://codereview.chromium.org/606513002

Cr-Commit-Position: refs/heads/master@{#296748}

BUG=265583

Review URL: https://codereview.chromium.org/596923002

Cr-Commit-Position: refs/heads/master@{#296747}

BUG=

Review URL: https://codereview.chromium.org/603753003

Cr-Commit-Position: refs/heads/master@{#296746}

Failed "check_licenses"

This reverts commit 6589af68.

BUG=416983
TBR=dmazzoni@chromium.org

Review URL: https://codereview.chromium.org/606653005

Cr-Commit-Position: refs/heads/master@{#296745}

TEST=Run chrome with and without the --enable-chromevox-next flag; observe injection occurs always for classic and only on non-whitelisted pages for next.

Review URL: https://codereview.chromium.org/599193002

Cr-Commit-Position: refs/heads/master@{#296744}

BUG=417534

Review URL: https://codereview.chromium.org/604893002

Cr-Commit-Position: refs/heads/master@{#296743}

This was causing many ResourceProviders to be created with distance field text randomly set to on or off.  Because AcquireSkSurface was never called on those instances of ResourceProvider, it isn't a serious problem, but I fixed it anyway, safer this way.

Review URL: https://codereview.chromium.org/601243003

Cr-Commit-Position: refs/heads/master@{#296742}