-
Notifications
You must be signed in to change notification settings - Fork 7
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
problem with installation and running tests #106
Comments
Apologies for the lack of clarity. I mentioned in #95 (comment) that the version under review is 0.8.0 of the software, compatible with dolfinx nightly (as the 0.8.0 is not released, although it is a few days away). There were some API changes over the last few days in the main branch, which I have addressed in: #107. These have just been merged into the main branch. Here is the way I tested this locally: docker pull ghcr.io/fenics/dolfinx/dolfinx:nightly
docker run -ti -v $(pwd):/root/shared -w /root/shared --rm ghcr.io/fenics/dolfinx/dolfinx:nightly Then either install adios4dolfinx with: python3 -m pip install adios4dolfinx[test]@git+https://github.com/jorgensd/adios4dolfinx@main or python3 -m pip install -e .[test] if you have the repository locally (remember to pull the main branch for the latest changes added 10 minutes ago). Then run tests with python3 -m pytest -xvs . or mpirun -n 2 python3 -m pytest -xvs . |
@gonsie Let me know if this clarifies and resolves your issue:) |
Thanks, with the nightly build I have been able to run the parallel and serial versions of the tests. Not sure if you're expecting all tests to pass... I got these results:
Thanks. |
I am expecting all tests to pass. You can see that they are executed on CI at every run: I just re-ran the commands I posted in the previous post, and they all pass for me. |
I ran the following:
The first failed serial run was:
first failed parallel test:
|
I cannot reproduce those error messages running the exact commands you sketched above: root@6efd03467dae:~/adios4dolfinx# history
1 python3 -m pip install adios4dolfinx[test]@git+https://github.com/jorgensd/adios4dolfinx@main
2 git clone https://github.com/jorgensd/adios4dolfinx.git
3 cd adios4dolfinx
4 python3 -m pytest -vs .
5 mpirun -n 2 python3 -m pytest -vs .
6 history Could you print the output of: python3 -c "import dolfinx; print(dolfinx.git_commit_hash)" Also what kind of system are you running on? |
I also cannot reproduce those error messages using the commands:
In the serial case I get
and the parallel case
For completeness I also see:
My host device is running Ubuntu 22.04.4 LTS |
I see:
I'm running the container on a Red Hat Enterprise Linux v8.9 HPC system. |
Very strange... It would be interesting to see if it can be reproduced with conda on your system once: I do unfortunately not have a Red Hat system to try to reproduce this on. |
What MPI is installed on your HPC system? |
Other relevant questions:
|
Is there a user manual for your hpc system that i could consult? |
I'm using the poodle system at LLNL, intel CPUs. Of note, I'm also using podman rather than docker directly, so there may be some issues there. That or an MPI issue would be the first places I would look. However, I'm not really interested in debugging this further. I'm happy to share the list of tests that are failing, if that would be helpful. |
It would be interesting to find out what is wrong, but it is unlikely that i will have a similar system to replicate that setup on. Therefore I’ll close this issue. |
This is related to openjournals/joss-reviews#6451.
I'm trying to install using the docker instructions, found on this page. I've been able to get a dolfinx image running, and install an adios4dolfinx package, but I can't run any successful tests.
I've run:
Then within the container I have tried various ways to install adios4dolfinx:
Both still require me to manually install ipyparallel (which seems like I shouldn't have to from the instructions).
But installing with pip doesn't quite get me to a test environment, so I've separately cloned the repo and tried running the tests:
gives the following errors:
I appreciate your assistance.
The text was updated successfully, but these errors were encountered: