Skip to content
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

Some tests fail #324

Open
yurivict opened this issue Oct 16, 2021 · 9 comments
Open

Some tests fail #324

yurivict opened this issue Oct 16, 2021 · 9 comments

Comments

@yurivict
Copy link

Describe the bug
See log.

Version: 0.20.1
OS: FreeBSD 13 (installed from the package)

@loriab
Copy link
Collaborator

loriab commented Oct 18, 2021

That's peculiar -- it looks like you're getting a memory segfault whenever nwchem invoked. You're running 7.0.2 but nwchem 7.0.0 from Ubuntu was fine in our testing https://github.com/MolSSI/QCEngine/runs/3840808437#step:4:211 . When did you last have this running correctly, v0.20.0 or v0.19.0 (or is this the first packaging?)? There was a change in 0.20 in how mem was passed to nwc, but I confirmed the new way to work with v5 and v7.

@yurivict
Copy link
Author

When did you last have this running correctly, [...]

The FreeBSD port didn't run tests before. I just added the ability to run tests and discovered this problem.

@WardLT
Copy link
Collaborator

WardLT commented Oct 18, 2021

The memory segfault is surprising and I'm puzzled by it.

I can point out another problem is that the NWChem is not compiled with Python support. That's currently required by QCEngine to compute gradients with NWChem. You can see that issue in how many of the tests crash with

python_input is not in this build of NWChem

in the STDOUT.

@yurivict
Copy link
Author

I can point out another problem is that the NWChem is not compiled with Python support.

I didn't realize that NWChem has Python support.
The Arch Linux port doesn't enable python support either.

Do you know how to enable python support in NWChem?

@WardLT
Copy link
Collaborator

WardLT commented Oct 18, 2021

It should be pretty straightforward. I don't have my Makefiles on hand (filesystems at ALCF are down for maintence), but you should be able to set the PYTHONVERSION environment variable to the major.minor version of Python in your environment.

For further details: https://nwchemgit.github.io/Compiling-NWChem.html#setting-python-environment-variables

@yurivict
Copy link
Author

MPI was broken on that machine.
I fixed MPI, added the PYTHON option to nwchem, and updated the test log in the URL in my OP.

@loriab
Copy link
Collaborator

loriab commented Oct 22, 2021

could your geometric be very old? all those tests are failing. they don't have any exactly new releases, but I could believe that anything less than the latest wasn't fully compatible with qca. https://github.com/leeping/geomeTRIC/tags

@yurivict
Copy link
Author

geomeTRIC is of the latest version 0.9.7.2 released in 2019. Maybe qcengine expects the current revision? They didn't have any releases after 2019.

Also log contains NWChem SEGVs. They probably should be reported to nwchem but it's unclear how to reproduce them.

@yurivict
Copy link
Author

0.21.0 test failures py38-qcengine-0.21.0-test.log

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

No branches or pull requests

3 participants