only run FlexiBLAS tests with NETLIB backend to verify mapping between FlexiBLAS and backend libraries #2426
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(created using
eb --new-pr)This is based on trouble I've been running into, especially on CPU architectures like
aarch64andppc64le, mostly with hanging tests (likexlintstsandxeigtstd).I got some feedback from the FlexiBLAS maintainer @grisuthedragon on this, and it's actually sufficient to only run the tests with the NETLIB backend (which is the default for the tests), to verify that the "mapping" aspect of FlexiBLAS is fully working.
Trouble with the tests (like hangs or very slow running tests) when using another BLAS/LAPACK backend is due to problems with the backend themselves, not with FlexiBLAS...