This test was missing the target triple, which was exposed by an
upcoming bugfix that requires getting the target earlier in the LTO API.
Once I fixed that, the case with the invalid character error stopped
returning 1 from llvm-lto2 and the test reported a failure. Fixed by
adding the missing return from llvm-lto2. Apparently we were failing
when we eventually tried to get the target.