0.15.0 test suite warnings

After installing 0.15.0, I ran the test cases with the following results:
========== 737 passed, 29 skipped, 702 warnings in 650.45s (0:10:50) ===========
all the warnings are IDWarnings, for example:
IDWarning: Another Tally instance already exists with id=2.
IDWarning: Another TallyDerivative instance already exists with id=1.
IDWarning: Another Surface instance already exists with id=10000.
IDWarning: Another Surface instance already exists with id=10001.
IDWarning: Another Universe instance already exists with id=6361.
IDWarning: Another WeightWindows instance already exists with id=1.

There is no report on which cases that were skipped.

What is causing the warnings and the skipped cases?

Hi Sharp, Wellcome to openmc community.
Could you explain how you did the test suite? Those warnings usually appear when another cell, surfaces, tally, etc with that id already exists in the xml files. So it might come from how the test suite manages the xml file in your pc and starts each test case.

Hi Wahid,

I am running the pytest script inside the /tests folder.
I have it running as a slurm job: mpi = 1, omp tasks=2

Hi Sharp,
actually, I have also encountered a similar failure when doing pytest in the /tests folder, and I couldn’t resolve the problem even after reading the test suite documentation provided in the folder openmc/docs/source/devguide/test.rst
even the pytest itself didn’t work well in my setup, hehe

but I have done some calculations with openmc, and it shows some consistency with other lattice codes.
So if these errors with pytest didn’t bother you, you could skip this part and start on your case problem, then do some code-to-code validation and verification with experimental data or benchmark case. Because I think it will be good to compare your calculation with other codes, benchmark data, or experiments.
if you are new to openmc, I recommend you to start with some example notebooks from this url

or test run some examples in openmc/examples folder by using command python3 filename.py, i.e from /jezebel folder, you could do

python3 jezebel.py

In the meantime, I think other members will gave comments on this topic later, especially one that successfully did the test suite using pytest.