-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures on s390x #586
Comments
I'm also seeing similar failures on 32-bit i686 |
Howdy Orion! Firstly we are up to version 4.1.0, so you might as well be working with the latest version. But I don't know how to test on machine of different endianness. Does GitHub offer any platform that would help? |
Actually, looks like you are at version 2.1.0 - I think we both got confused there. Github does not appear to offer any s390x hosts for CI. I can build and run anything on a Fedora s390x machine - so let me know what would be helpful. |
Yes, I meant 2.1.0. But nonetheless, I cannot hope to get g2 to work on a platform I don't have access to for testing. Try running one of the failing tests from the command line and see if the output says anything useful. |
So, with tst_inq it seems like it in trying to seek past the end of the file. strace shows:
I enabled some logging:
|
In g2c_seekmsg (g2cid=1, skip=0, offset=0x3ffffff6d80, msglen=0x3ffffff6d78) at /builddir/build/BUILD/g2clib-2.1.0-build/NCEPLIBS-g2c-2.1.0/src/g2cfile.c:87:
|
I'm looking to update the Fedora g2c library package to 2.1.0 but I'm getting the following test failures on s390x:
This is likely due to the different endianness of s390x. There is not a lot of output from the tests so hard to know what is going on. Can we get more output?
The text was updated successfully, but these errors were encountered: