-
Notifications
You must be signed in to change notification settings - Fork 150
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
Fix ubuntu-latest CI and introduce Arm validation #1165
Conversation
b3b1e7a
to
030680e
Compare
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
Signed-off-by: Igor S. Gerasimov <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checks all seem to be passing now, so this looks good to go.
Is there any particular reason to introduce ARM checks? |
Some guys uses xtb in AWS cloud. Would be nice to check that at least tests are correct for them. :-) And you can see that different sets are failing on x86 and Aarch64 in Debug mode. |
I will revert this once the runners with 24.04.5 are fully rolled out (as they have pre-installed LAPACK). Additionally, I will reduce the number of tests—IMO, gfortran 10 and 12 are outdated. |
Broken tests with CMake + Debug, so these build are currently disabled:
on x86_64:
on Aarch64: