Stop disabling building of partly_invalid.nexe in a corner case

Stop disabling building of partly_invalid.nexe in a corner case

The odd linking problem that only occurred on one trybot (and which I
couldn't reproduce locally) in the IRT+glibc case has gone away --
perhaps following toolchain updates -- so re-enable this case.

This is in preparation for making all of chrome_browser_tests build in
nacl_irt_test_env rather than nacl_env, for uniformity.  One of these
tests uses partly_invalid.nexe.  Without this change, the change
https://codereview.chromium.org/11613012/ fails with:

scons-out/nacl_irt_test-x86-64-glibc/staging/partly_invalid.nmf.libs
failed: Source
`scons-out/nacl_irt_test-x86-64-glibc/staging/partly_invalid.nexe' not
found, needed by target
`scons-out/nacl_irt_test-x86-64-glibc/staging/partly_invalid.nmf.libs'.

BUG=https://code.google.com/p/nativeclient/issues/detail?id=3253
TEST=trybots

Committed: https://src.chromium.org/viewvc/native_client?view=rev&revision=10568

[Nick Bray (chromium), 2013-01-10 18:30:52]

LGTM

Could this be related to the empty .o files issues reported on nacl-eng?

[Mark Seaborn, 2013-01-10 19:11:06]

On 2013/01/10 18:30:52, Nick Bray (chromium) wrote:
> Could this be related to the empty .o files issues reported on nacl-eng?

I don't think so.