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

CI: Revert breaking change to valgrind test #192

Closed

Conversation

elykwilliams
Copy link
Contributor

Revert breaking change to valgrind CI test

It looks like the Valgrind test will need some updating before bumping the OS to Ubuntu 24.04. I'm not sure why but as the logs show, it's failing to successfully install the system packages. Related to #185. Breaking Commit was 0c3a681.

Proposed changes:
I've reverted the OS to Ubuntu 22.04 for the valgrind test, until I can give it a closer look #191 .

@cburstedde
Copy link
Owner

Thanks, is there anything we can do about the faliing test on Mac with gcc 13?

@elykwilliams
Copy link
Contributor Author

Thanks, is there anything we can do about the faliing test on Mac with gcc 13?

I'm looking into it. It's strange because the bump to gcc-13 happened back in December, so that by itself isnt the problem. But the issue seems to be that cmake isn't finding a compatible version of mpi, even though it is finding the homebrew installed open-mpi.

@cburstedde
Copy link
Owner

Maybe @scivision can help.

As soon as possible, I'd like to establish to only use software (like valgrind and CMake) no newer than what's in the current Debian stable distribution. For CMake that's 3.25.

@cburstedde
Copy link
Owner

cburstedde commented Jun 19, 2024

Should I just merge this one since it CI checks fine? Ah wait, the MacOS gcc13 test is the issue.

@cburstedde
Copy link
Owner

Maybe @scivision can help.

As soon as possible, I'd like to establish to only use software (like valgrind and CMake) no newer than what's in the current Debian stable distribution. For CMake that's 3.25.

That would also mean using at most gcc-11. Would anything speak against this policy, specifically for p4est and sc?

@cburstedde
Copy link
Owner

I'm also wondering about specifying CC= in the CI CMake. With MPI, the compiler should always be mpicc -- is this silently added by the CMake MPI logic, or do we need to do something about it?

@scivision
Copy link
Contributor

I think this PR can be closed; this was a transient issue in the new Ubuntu 24.04 image.
#194 shows Valgrind working with Ubuntu 24.04

@cburstedde
Copy link
Owner

I think this PR can be closed; this was a transient issue in the new Ubuntu 24.04 image. #194 shows Valgrind working with Ubuntu 24.04

Ok closing here. Thanks for the report/initiative @elykwilliams !

@cburstedde cburstedde closed this Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants