Skip to content

Conversation

@brownbaerchen
Copy link
Contributor

The features from Gusto that we use here work again with the most recent Firedrake, so I switched the pipeline to use the latest Firedrake docker container. (@jshipton)
Also, black had an update and required some reformatting...

runs-on: ubuntu-latest
container:
image: firedrakeproject/firedrake-vanilla:2025-01
image: firedrakeproject/firedrake-vanilla:latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is dangerous. You don't know what the next stage will bring.. can you pin the version to something?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

un-pinning the version is precisely the point of this PR. The Gusto pipeline runs on the latest Firedrake, so if we pin Firedrake but not Gusto, we might get into trouble. If we pin both, we make sure that the current state runs now, but people may not be able to install the current Firedrake outside of containers in the future.
I suggest we test on the latest Firedrake and revert to a specific version if something fails that we cannot fix easily.
What is your take @jshipton, you have more experience on being dependent on Firedrake ;)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @brownbaerchen - that seems to be the sanest option

@pancetta pancetta merged commit c13d5a5 into Parallel-in-Time:master Feb 4, 2025
87 checks passed
@brownbaerchen brownbaerchen deleted the firedrake_CI_update branch March 31, 2025 08:27
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