Test Failures After Reinstalling MOOSE (Preparing for TMAP8 Installation)

[katielygre]

Hello,

@cticenhour pointed me to this discussion forum—thank you!

Previously, I was only able to run MOOSE using a user-specific installation. I'm now trying to work with TMAP8 and encountered some issues. To start fresh, I uninstalled both TMAP8 and MOOSE, removed my MOOSE conda environment, and then reinstalled MOOSE following the installation guide.

However, I'm now failing many tests during the "Build and Test MOOSE" step:

How should I go about resolving these test failures, if needed, before attempting to install TMAP8 again?

Here is an output log: make_output.log

Thanks in advance for your help!

[cticenhour]

I keep seeing variations of the following output error in your log output:

/groupspace/cnerg/users/lygre/projects/moose/test/tests/auxkernels/projection_aux/1d.i:404.3:
The following error occurred in the Output 'exodus' of type Exodus.

MOOSE failed to remove the empty file 1d_constant.e

This is a fundamental capability, which shouldn't be failing....which makes me think we have a corrupted library at the MOOSE level.

Can you give me the output of running the diagnostics.sh script located in moose/scripts?

[cticenhour]

Thanks for the context, Paul! Let me know if we need to make any changes to how we're doing the file removal on our side.

[gonuke]

Hmmm... it's become even more mysterious... In the process of doing some testing, we found that subsequent runs of

./run_tests --re="outputs/ex*" -j1

They will all pass sometimes and then some of them won't pass another time. My above hypothesis about disk volumes seems to have been a red herring.

[simopier]

I'm trying to clean up the discussions here and mark them as answered or closed whenever possible.
@katielygre, @gonuke: Is this still an issue? Or was this somehow resolved?

[simopier]

It seems like this is not an issue anymore and might have been caused by local disk volume issues.

Feel free to revive this discussion if the problems resurfaces.