Commit 93899eed authored by rouslan@chromium.org's avatar rouslan@chromium.org

Revert of NaCl: Update revision in DEPS, r13309 -> r13318...

Revert of NaCl: Update revision in DEPS, r13309 -> r13318 (https://codereview.chromium.org/324353002/)

Reason for revert:
The change appears to have broken http://build.chromium.org/p/chromium.chrome/buildstatus?builder=Google%20Chrome%20ChromeOS&number=68537.

Original issue's description:
> NaCl: Update revision in DEPS, r13309 -> r13318
> 
> This pulls in the following Native Client changes:
> 
> r13310: (dyen) Commands for toolchain_build are now filtered before invoking anything.
> r13311: (dyen) Fix for needing to push to ssh URL for toolchain_build sources.
> r13312: (mcgrathr) Disable seccomp-bpf tests under ASan
> r13313: (mcgrathr) Disable LSan (leak detection) in ASan tests
> r13314: (mseaborn) Enable the -Wstrict-prototypes warning for untrusted code in the Gyp build
> r13315: (dyen) Python logging now organized to use loggers instead of global variables.
> r13316: (jfb) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
> r13317: (jfb) Update revision for PNaCl r13281->r13311
> r13318: (jfb) Update revision for PNaCl r13311->r13316
> 
> BUG=none
> TEST=browser_tests and nacl_integration
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=276475

TBR=bradnelson@google.com,mseaborn@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=none

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@276479 0039d316-1c4b-4281-b951-d872f2087c98
parent 5bfaab73
......@@ -34,7 +34,7 @@ vars = {
"pdfium_git": "https://pdfium.googlesource.com",
"skia_git": "https://skia.googlesource.com",
"swig_revision": "230490",
"nacl_revision": "13318",
"nacl_revision": "13309",
# After changing nacl_revision, run 'glient sync' and check native_client/DEPS
# to update other nacl_*_revision's.
"nacl_tools_revision": "13077", # native_client/DEPS: tools_rev
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment