Fixes for big-endian platforms - #60
Conversation
Codecov Report
@@ Coverage Diff @@
## master #60 +/- ##
=======================================
Coverage 98.02% 98.02%
=======================================
Files 79 79
Lines 5105 5105
=======================================
Hits 5004 5004
Misses 101 101
Continue to review full report at Codecov.
|
|
I'm testing it right now (UtilityDirectoryTest has been running for the last 10 minutes, is that normal)? One test that failed so far is: You won't able to test for POWER9 (this is like testing specifically for Skylake or Ryzen, you need to ping kernel directly for that), but you can test for POWER: |
|
OK, it finished. The only failing tests are: The 1st is mentioned above, the 2nd you can fix by checking e.g. for |
So they skip the test instead of polluting the filesystem with random files and then complaining that it didn't fail.
|
Thanks a lot! 👍 The
Yeah sorry there's a little benchmark comparing various file copy approaches. It runs in a second on a SSD and in around five seconds on a HDD. Didn't expect it to run on such a device, so that's why 😅 I force-pushed an updated version, if you could do one last check with just the two formerly failing tests, like this, would be great. Thanks for all your help! 👍 ctest --output-on-failure -R (SystemTest|StridedArrayViewTest) |
|
All tests have passed. |
|
Likewise, thanks for the confirmation! :) |
Should cover everything reported in #58 (and https://pastebin.com/GkSgVGyd), except the System test, as I have no idea what preprocessor macros to use to detect a Power9 architecture. I'm also a bit unsure about the SHA-1 fix, but hopefully it's the correct place to make that change.
@pkubaj would be wonderful if you could run the tests again on this branch 🙏 thanks in advance!