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

New CI with Github Actions #329

Open
wants to merge 16 commits into
base: develop
Choose a base branch
from

Conversation

simonlegrand
Copy link
Contributor

Here is a first contribution to the new FreeFem CI.

5 different configurations of FreeFem are tested:

  • Minimal version
  • Sequential version (with all dependencies)
  • Full version OpenMPI
  • Full version MPICH
  • Full version MS-MPI

Each of these workflows contains jobs for Debug and Release and different combinations of platforms.

Currently, the build step doesn't work for the following configuration:

  • Sequential/Windows/Debug
  • Full Version MS-MPI/Debug
  • Full Version OpenMPI/MacOS-14/*

But most of the tests should fail because of the removal of the continue-on-error: true at the make check step (few tests fail for almost each config). It can be temporarily put back if you prefer.

At first, if you prefer to merge on a different branch, just add the branch name in the

on:
  push:
    branches:
      ..
      - <branch_name>

Finally, due to the particular development workflow (push to test), the commit history is particularly dirty and should probably be squashed before the merge. It can be retrieved here

Cheers,
Simon

@prj-
Copy link
Member

prj- commented Dec 20, 2024

Why do you need to install SuiteSparse explicitly when building PETSc? Can't you let PETSc install it? Also, there are a couple of parallel packages in the sequential installs (ParMmg, ParMETIS, to name a few).

@simonlegrand
Copy link
Contributor Author

Bien vu, I stupidly copy paste former tests. I'm not completely familiar with all the dependencies, can you confirm that I didn't leave anything uselss?

@simonlegrand
Copy link
Contributor Author

Thanks ;)

@simonlegrand simonlegrand force-pushed the slegrand-actions branch 3 times, most recently from e100e87 to 6c11b37 Compare January 17, 2025 16:20
@simonlegrand
Copy link
Contributor Author

Three previous comments fixed in 92027eb

@prj- prj- force-pushed the slegrand-actions branch 2 times, most recently from f27fbdd to 3a5c86b Compare January 30, 2025 15:27
@FreeFem FreeFem deleted a comment from sonarqubecloud bot Jan 30, 2025
@prj- prj- force-pushed the slegrand-actions branch 6 times, most recently from 93c41a2 to daba3d8 Compare February 4, 2025 17:03
@simonlegrand simonlegrand force-pushed the slegrand-actions branch 3 times, most recently from dc77ce3 to 089d568 Compare February 13, 2025 17:15
- Don't seem to impact CI directly
- Most appear to be formatting changes
Each workflow contents several jobs (Debug/Release + plateforms)
@simonlegrand simonlegrand force-pushed the slegrand-actions branch 3 times, most recently from 994112c to d02ddc3 Compare February 26, 2025 12:24
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.

2 participants