Skip to content
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

7 VDS Example Tests Fail on Big Endian Machines #4069

Closed
hyoklee opened this issue Mar 5, 2024 · 2 comments
Closed

7 VDS Example Tests Fail on Big Endian Machines #4069

hyoklee opened this issue Mar 5, 2024 · 2 comments
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Improvement Improvements that don't add a new feature or functionality
Milestone

Comments

@hyoklee
Copy link
Member

hyoklee commented Mar 5, 2024

Describe the bug

CTest fails on big endian machines.
They are 7 VDS example tests.

Expected behavior

All tests pass.

Platform (please complete the following information)

  • HDF5: develop branch
  • OS and version: 3.10.0-1160.36.2.el7.ppc64
  • Compiler and version: gcc
  • Build system (e.g. CMake, Autotools) and version: ctest-3.29.0-rc2

Additional context

https://my.cdash.org/viewTest.php?onlyfailed&buildid=2511204

@derobins derobins added Merge - To 1.14 Priority - 1. High 🔼 These are important issues that should be resolved in the next release Component - Testing Code in test or testpar directories, GitHub workflows Type - Improvement Improvements that don't add a new feature or functionality labels Mar 5, 2024
@derobins
Copy link
Member

derobins commented Mar 5, 2024

These tests fail because the tests use H5T_NATIVE_INT for the dataset's type, which we then diff with the output from a little-endian machine. It's easily fixed by specifying a little-endian type for the dataset.

@derobins derobins added this to the 1.14.4 milestone Mar 7, 2024
@derobins
Copy link
Member

derobins commented Mar 7, 2024

Fixed in #4070

@derobins derobins closed this as completed Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Improvement Improvements that don't add a new feature or functionality
Projects
None yet
Development

No branches or pull requests

2 participants