-
Notifications
You must be signed in to change notification settings - Fork 47
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
Ensure Espresso recipes work without calls to os.chdir
#1807
Comments
## Summary of Changes Fix for #1807 Please do not hesitate to ping me on this kind of issues ### Checklist - [ ] I have read the ["Guidelines" section](https://quantum-accelerators.github.io/quacc/dev/contributing.html#guidelines) of the contributing guide. Don't lie! 😉 - [ ] My PR is on a custom branch and is _not_ named `main`. - [ ] I have added relevant, comprehensive [unit tests](https://quantum-accelerators.github.io/quacc/dev/contributing.html#unit-tests). ### Notes - Your PR will likely not be merged without proper and thorough tests. - If you are an external contributor, you will see a comment from [@buildbot-princeton](https://github.com/buildbot-princeton). This is solely for the maintainers. - When your code is ready for review, ping one of the [active maintainers](https://quantum-accelerators.github.io/quacc/about/contributors.html#active-maintainers).
Reopening this issue because it's not fully solved just yet. See here. Will update with more details. Edit: Seems like the issue is with The
Files: @tomdemeyere: if you have any ideas, I'm all ears! |
Ah, weird, do you have an idea why this was not showing up in the test of my previous PR? (knowing this might help me deal with it) EDIT: stupid question sorry, I got it I didn't run test on the proper branch |
Details about the quacc environment
What is the issue?
In my ongoing attempt to make
quacc
safe for multithreading by removingos.chdir
calls, it appears that Espresso is one of the remaining sets of recipes that are not compatible.How can we easily reproduce the issue?
See here.
The text was updated successfully, but these errors were encountered: