-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
add nwchem #14725
add nwchem #14725
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/nwchem:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Your patch did change something - this was the error before:
error after (no longer tries to read from non-existing file):
What puzzles me is the original error message
This reads like nwchem is trying to look for the basis sets in the
is not picked up by the tests? However, I can't quite square that with the fact that your patch seems to have made the error message go away (the path to the |
thanks @edoapra , I've added your second patch but the error message seems to stay (almost) the same (not sure whether the repetition of
|
@ltalirz Could you
|
for unknown reasons, nwchem thinks the C compiler binary is `gcc`, despite a different value of the CC environment variable. Let's see whether exporting the value makes any difference...
first without passing it to make explicitly. if that doesn't help, we'll need to do that as well
probably created somewhere else - blas problem should anyhow be solved
if that doesn't help, we'll need to figure out how to pass the `--oversubscribe` option to `mpirun`
sure! by the way, I've also invited you as a collaborator to my fork in case you'd like to try any changes directly |
I think the relevant bits are
I guess in the first case the output is somehow cut short - this looks like the correct path (but nwchem fails to read it because the path is too long). I will now add it to the $SRC directory and point nwchem there. |
Looks to me like we're getting close... now I get
Is there a way to see a more verbose output of the parsing script? |
Do you have
PS:I have managed to reproduce this error message by unistalling |
You would suggest |
I guess I'll wait until the tests pass on edoapra/nwchem@c8e634a before including the patch |
but no |
Right. The first logs are promising since they show no errors when using |
It should not be needed, but it would not hurt to add it. In other words
You might want to add
|
On the previous commit it looks to me like the tests are passing, i.e. I think there is hope that we've arrived! As mentioned previously, if you'd like to be added as a co-maintainer of this conda-forge feedstock, just let me know. |
@conda-forge/staged-recipes Sorry for asking but I've done a couple of feedstocks by now and this has never happened to me: We just managed to make the If you look at the raw logs (output is already a bit long for the interactive one) and search for Any ideas what might be causing this? |
The runs are marked at successful now (after more than 5 hours). |
Hmm I can no longer access the logs from https://github.com/conda-forge/staged-recipes/runs/2522601261 (build not found ). Let's maybe wait for someone from @conda-forge/staged-recipes to have a look before I start doing something that ends up removing the latest logs as well. |
According to
|
Ok, for the record I'm attaching the raw log output of https://github.com/conda-forge/staged-recipes/runs/2522963263 : Will now restart the build to see what happens. |
That's for each python version. (3.6, 3.7, 3.8, 3.9) |
Thanks a lot for the hint @isuruf ! @edoapra the python dependency under if not, I can remove it from |
Yes, NWChem does have python interface. |
Thanks! That leads me to some follow-up questions:
|
|
Thanks, in that case the individual builds for the different python versions may be necessary. Perhaps the conda-forge maintainers have another/better suggestion for this. |
@conda-forge/staged-recipes, ready for review |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).