-
Notifications
You must be signed in to change notification settings - Fork 193
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
base: develop
Are you sure you want to change the base?
Conversation
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). |
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? |
Thanks ;) |
e100e87
to
6c11b37
Compare
@@ -260,7 +267,7 @@ sub downloadone{ | |||
system $cmd; | |||
if($?){ | |||
print "Download failed from $url of $pkg\n"; | |||
my $url="https://www.ljll.fr/hecht/pkg/$pkg"; | |||
my $url="https://joliv.et/freefem/pkg/$pkg"; |
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.
Is this really needed in the end?
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.
It seems the dependencies download problems have been solved by this fix. I'd keep it if it's ok for you.
- Don't seem to impact CI directly - Most appear to be formatting changes
Each workflow contents several jobs (Debug/Release + plateforms)
6c11b37
to
69d7895
Compare
Quality Gate passedIssues Measures |
Three previous comments fixed in 92027eb |
Here is a first contribution to the new FreeFem CI.
5 different configurations of FreeFem are tested:
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:
But most of the tests should fail because of the removal of the
continue-on-error: true
at themake 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
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