NaCl: Update revision in DEPS, r14178 -> r14201

NaCl: Update revision in DEPS, r14178 -> r14201

This pulls in the following Native Client changes:

r14179: (kschimpf) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14180: (ncbray) GN: fix layering of library dependencies.
r14181: (shyamsundarr) enable all nonspecial avx1 instructions.
r14183: (dschuff) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14184: (dschuff) Use an architecture-specific newlib build for nacl-clang
r14185: (dschuff) Make libc.a a linker script for nacl-clang
r14186: (jvoung) Don't use pnacl raw toolchain in llvm nightly and libcxx tests.
r14187: (hamaji) Non-SFI Mode: Build PIE nonsfi_loader
r14188: (dschuff) Update revision for PNaCl r14173->r14185
r14189: (dschuff) PNaCl: Update Clang revision in pnacl/COMPONENT_REVISIONS
r14190: (jvoung) Remove a few locale-related "known failures" from libcxx list.
r14191: (dyen) NaCl Core SDK libs for both x86-32/x86-64 x86 newlib/glibc toolchains.
r14192: (sbc) Update glibc version in tools/REVISIONS (f78e18e->1106743)
r14193: (dyen) Fixed package_version reusing work dirs between revision packages.
r14194: (ncbray) Roll GCC toolchains.
r14195: (hidehiko) Non-SFI mode: Override NACL_BUILD_ARCH and _SUBARCH in build_nexe.py.
r14196: (dschuff) Remove cygwin support from buildbot_pnacl_toolchain.py
r14197: (jvoung) PNaCl: Update LLVM revision in pnacl/COMPONENT_REVISIONS
r14198: (sbc) ncval_new: on success don't produce any output by default.
r14200: (ncbray) GN: do not assemble toolchain in output directory.
r14201: (grt) Stop closing thread handles owned by the Win32 debugging API.

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

Committed: https://crrev.com/838194227ff0c1a35a15d77cee8e1d76bd115070
Cr-Commit-Position: refs/heads/master@{#308091}

[grt (UTC plus 2), 2014-12-11 15:30:07]

grt@chromium.org changed reviewers:
+ mseaborn@chromium.org

[grt (UTC plus 2), 2014-12-11 16:05:26]

NaClBrowserTestPnacl.PnaclErrorHandling seems to be failing with this roll on
linux_chromium_rel_ng. Any ideas from those with native_client changes in the
range?

[jvoung - send to chromium..., 2014-12-11 16:51:40]

On 2014/12/11 16:05:26, grt wrote:
> NaClBrowserTestPnacl.PnaclErrorHandling seems to be failing with this roll on
> linux_chromium_rel_ng. Any ideas from those with native_client changes in the
> range?

I'm thinking it is 14188, which brought in a bunch of PNaCl changes.

In the log:

[1136:5152:1211/080956:INFO:nacl_browsertest_util.cc(131)] |||| [bad_pexe BEGIN]
[4700,4116:16:09:56.592000] Native Client module will be loaded at base address
0x000001f800000000
[1136:5152:1211/080956:INFO:CONSOLE(0)] "NativeClient: PnaclCoordinator: PNaCl
Translator Error: Error: Invalid PNaCl bitcode header
Error in bitstream format", source:
http://127.0.0.1:55854/files/pnacl_error_handling.html?pnacl=1 (0)
[1136:5152:1211/080956:INFO:nacl_browsertest_util.cc(131)] |||| [bad_pexe FAIL]
('NaCl module load failed: PnaclCoordinator: PNaCl Translator Error: Error:
Invalid PNaCl bitcode header
Error in bitstream format' != 'NaCl module load failed: PnaclCoordinator: PNaCl
Translator Error: Invalid PNaCl bitcode header')

Namely, the last line of that shows that the expected message is different from
the given message now.

Some of the error reporting has changed recently.

[grt (UTC plus 2), 2014-12-11 18:38:37]

On 2014/12/11 16:51:40, jvoung - send to chromium... wrote:
> On 2014/12/11 16:05:26, grt wrote:
> > NaClBrowserTestPnacl.PnaclErrorHandling seems to be failing with this roll
on
> > linux_chromium_rel_ng. Any ideas from those with native_client changes in
the
> > range?
> 
> I'm thinking it is 14188, which brought in a bunch of PNaCl changes.

Thanks for the pointer. I think I've updated the test expectation accordingly.
Please take a look.

[jvoung (off chromium), 2014-12-11 18:58:14]

jvoung@chromium.org changed reviewers:
+ jvoung@chromium.org

[jvoung (off chromium), 2014-12-11 18:58:14]

LGTM thanks

[grt (UTC plus 2), 2014-12-11 20:59:47]

The CQ bit was checked by grt@chromium.org

[commit-bot: I haz the power, 2014-12-11 21:01:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/793383003/20001

[commit-bot: I haz the power, 2014-12-11 21:07:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-12-11 21:07:19]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Mark Seaborn, 2014-12-11 21:10:21]

LGTM

[grt (UTC plus 2), 2014-12-11 21:10:40]

The CQ bit was checked by grt@chromium.org

[commit-bot: I haz the power, 2014-12-11 21:12:02]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/793383003/20001

[commit-bot: I haz the power, 2014-12-12 09:03:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-12-12 09:03:19]

Exceeded time limit waiting for builds to trigger.

[grt (UTC plus 2), 2014-12-12 14:16:26]

What do you NaCl experts make of the RemoteDebuggingTest.RemoteDebugger failure
on linux_rel_precise32? Some interesting snippets from the log:

[4832:4832:1211/141620:INFO:CONSOLE(0)] "[FAIL] discoverTargets: API Test Error
in discoverTargets
Actual: chrome-extension://njkkjfehnhadoljcfdpgcmepldhngalc/test_page.html
Expected: Test page
Error

[4832:4832:1211/141620:INFO:CONSOLE(0)] "[SUCCESS] checkInspectablePagesUI",
source:
chrome-extension://njkkjfehnhadoljcfdpgcmepldhngalc/_generated_background_page.html
(0)
[4832:4832:1211/141620:INFO:CONSOLE(0)] "XMLHttpRequest cannot load
http://localhost:9222undefined/. Cross origin requests are only supported for
protocol schemes: http, data, chrome, chrome-extension, https,
chrome-extension-resource.", source:
chrome-extension://njkkjfehnhadoljcfdpgcmepldhngalc/_generated_background_page.html
(0)
[4832:4832:1211/141620:INFO:CONSOLE(0)] "[FAIL] checkDebuggerUI: XHR failed: 0

[grt (UTC plus 2), 2014-12-12 14:22:51]

On 2014/12/12 14:16:26, grt wrote:
> What do you NaCl experts make of the RemoteDebuggingTest.RemoteDebugger
failure
> on linux_rel_precise32?

Never mind. The flakiness dashboard tells me that it's just a flaky test.

[grt (UTC plus 2), 2014-12-12 15:07:28]

The CQ bit was checked by grt@chromium.org

[commit-bot: I haz the power, 2014-12-12 15:07:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/793383003/20001

[commit-bot: I haz the power, 2014-12-12 16:00:08]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-12-12 16:00:51]

Patchset 2 (id:??) landed as
https://crrev.com/838194227ff0c1a35a15d77cee8e1d76bd115070
Cr-Commit-Position: refs/heads/master@{#308091}