The test strings we used for infinity and NAN were not correct on AIX.
This patch creates those dynamically instead of hard-coded.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/unittests/Support/ScopedPrinterTest.cpp | ||
---|---|---|
598 | Dumb question maybe, but why the "5.1"? |
llvm/unittests/Support/ScopedPrinterTest.cpp | ||
---|---|---|
598 | "%5.1" is the format string we use in printNumber(). IIRC that was what was taken from existing code in ElfDumper. |
Hi @paulkirth, this testcase is still failing the same way on the AIX bot even after this change https://lab.llvm.org/buildbot/#/builders/214/builds/6557. Can this change be reverted until we figure out the proper fix?
Ugh, I see this issue. I missed that the "INF/inf" discrepancy also happens for JSON output, but only changed the non-JSON test string. I should have a forward fix very soon. If that causes issues, we'll either need to revert the original patch, the 2 fixes and the HasHistogram patch, or disable the test for float/double,until we sort it out.
If you really need the bot to progress, I'm fine w/ you reverting things, though.
@abhina.sreeskantharajan is there a way to test AIX things locally? i.e. as in run on a bot "somewhere"? or a simple QEMU image we can use, etc?
Thanks, I see you already put up a fix so we can see if that fixes it
I believe you can get access to AIX systems in GCC Compile Farm system http://gcc.gnu.org/wiki/CompileFarm
Dumb question maybe, but why the "5.1"?