NaCl: Update revision in DEPS, r13091 -> r13106

NaCl: Update revision in DEPS, r13091 -> r13106

This pulls in the following Native Client changes:

r13092: (dschuff) build_nexe.py: Handle Windows paths in deps file parsing
r13093: (dschuff) Add glob support to command.Remove, use to prune some libs from PNaCl tarball
r13094: (jvoung) Put a couple more tests in nonpexe_tests suite.
r13095: (mcgrathr) Update chrome_rev in DEPS
r13097: (mcgrathr) toolchain_build: Emit human-readable signature details in bot logs
r13098: (dyen) PNaCl buildbot arm gcc now uses symlinked version instead of 4.5
r13099: (jvoung) Run x86-64 scons tests on the PNaCl Mac toolchain builder.
r13100: (dyen) Made x86 newlib/glibc trybots also upload to trybot GSD bucket.
r13101: (noelallen) Roll Bionici
r13102: (dyen) Packages JSON format now has a version number associated to the format.
r13103: (noelallen) Roll bionic
r13104: (jfb) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r13105: (dschuff) PNaCl driver: Put intermediate temp files in system temp dir
r13106: (jfb) Update revision for PNaCl r13072->r13104

BUG=none
TEST=browser_tests and nacl_integration
R=bradnelson@google.com

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=267339

[bradn, 2014-04-30 18:45:29]

lgtm

[David Yen, 2014-04-30 19:50:15]

This roll should wait for this CL to be landed first:

https://codereview.chromium.org/268493003/

Once that has landed, I will do my package_version roll which involves both nacl
and chromium changes. This will reduce the number of CLs included within the
roll to a minimum.

[Mark Seaborn, 2014-04-30 19:53:46]

On 30 April 2014 12:50, <dyen@chromium.org> wrote:

> This roll should wait for this CL to be landed first:
>
> https://codereview.chromium.org/268493003/


I don't think that's essential, is it?  If I commit this roll as-is, it
just means we get a slightly older but still-working PNaCl toolchain.  This
DEPS roll won't break anything, will it?

Cheers,
Mark

-- 
You received this message because you are subscribed to the Google Groups
"Native-Client-Reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to native-client-reviews+unsubscribe@googlegroups.com.
To post to this group, send email to native-client-reviews@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-reviews.
For more options, visit https://groups.google.com/d/optout.

[Mark Seaborn, 2014-04-30 19:53:47]

On 30 April 2014 12:50, <dyen@chromium.org> wrote:

> This roll should wait for this CL to be landed first:
>
> https://codereview.chromium.org/268493003/


I don't think that's essential, is it?  If I commit this roll as-is, it
just means we get a slightly older but still-working PNaCl toolchain.  This
DEPS roll won't break anything, will it?

Cheers,
Mark

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[Derek Schuff, 2014-04-30 20:01:18]

On 2014/04/30 19:53:47, Mark Seaborn wrote:
> On 30 April 2014 12:50, <mailto:dyen@chromium.org> wrote:
> 
> > This roll should wait for this CL to be landed first:
> >
> > https://codereview.chromium.org/268493003/
> 
> 
> I don't think that's essential, is it?  If I commit this roll as-is, it
> just means we get a slightly older but still-working PNaCl toolchain.  This
> DEPS roll won't break anything, will it?

Correct. I think we should land this as-is, and then do another roll with the
package_version change. That is what will minimize the number of CLs within that
roll.

[Derek Schuff, 2014-04-30 20:04:04]

> Correct. I think we should land this as-is, and then do another roll with the
> package_version change. That is what will minimize the number of CLs within
that
> roll.

actually i misinterpreted your original statement. You meant you would do
another roll which would not include the pnacl version bump and only change the
download method.

Still, I think it's fine to land this if we get green bots; the pnacl roll is a
very small change and there are no relevant tests on the chrome side for it.

[Mark Seaborn, 2014-04-30 21:26:10]

Committed patchset #1 manually as r267339 (presubmit successful).