Skip to content

Update stage25 #544

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

Draft
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

jakob-fritz
Copy link
Collaborator

New PR to replace #525 , as I updated my master-branch, I accidentally closed the previous PR

jakob-fritz and others added 6 commits January 29, 2025 15:19
By this, also changed version of FFTW (as the previous one seems to  not be included in Stage 2025)
Force-Purge is normally not needed and can lead to strange behaviour
@pancetta
Copy link
Member

pancetta commented Jul 8, 2025

Do we still need this or is this obsolete?

@brownbaerchen
Copy link
Contributor

Well, I am still procrastinating dealing with this.. Maybe you can retrigger the actions to see if the stages have changed so it works now..? If yes, let's merge, if no, let's keep this open and deal with it eventually :D

@pancetta
Copy link
Member

pancetta commented Jul 8, 2025

Yeah. No.

@brownbaerchen
Copy link
Contributor

I have a virtual environment working with stage 2025. I suggest, we just switch to the sc venv template from Stefan here as well.
We set up the venv once with installations in editable mode and in the pipeline, we simply checkout the branches containing the latest changes.
What do you think @jakob-fritz?

@jakob-fritz
Copy link
Collaborator Author

I don't see a reason, why the approach should not work. Good idea, definitely worth a try, @brownbaerchen .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants