MOOSE install: successful build, but got failed tests #28461

frankwugeo · 2024-08-23T07:59:46Z

frankwugeo
Aug 23, 2024

Check these boxes if you have followed the posting rules.

I have consulted the Posting Guidelines.
I have searched the Discussions Forum and MOOSE Framework Troubleshooting and have not found what I was looking for
Q&A Getting Started is the most appropriate category for my question (trouble installing, beginner user, ...)

Issue or question about MOOSE

Hi MOOSE community,

I have followed the tutorial to install MOOSE on MacOS. I seem to have built MOOSE using make, but when I run the tests, it shows a lot of failed tests (50) and none of them pass.

Could anyone in the community please help with this issue? Some of the error outputs are listed below.

Cheers

(Optional) code in question / simulation log / errors

misc/check_error.dot_integrity_check: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.dot_integrity_check: Running command: /Users/me/projects/moose/test/moose_test-opt -i dot_integrity_check.i --error --error-override --libtorch-device cpu
misc/check_error.dot_integrity_check: ################################################################################
misc/check_error.dot_integrity_check: 
misc/check_error.dot_integrity_check: Unable to match the following pattern against the program's output:
misc/check_error.dot_integrity_check: 
misc/check_error.dot_integrity_check: Calling "coupled\[Vector\]\[Gradient/Dot\]Old\[er\]" on variable "\S+" when using a \"Steady\" executioner is not allowed. This value is available only in transient simulations.
misc/check_error.dot_integrity_check: 
misc/check_error.dot_integrity_check: ################################################################################
misc/check_error.dot_integrity_check: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.dot_integrity_check: 
misc/check_error.dot_integrity_check ......................................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.function_file_test11: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.function_file_test11: Running command: /Users/me/projects/moose/test/moose_test-opt -i function_file_test11.i --error --error-override --libtorch-device cpu
misc/check_error.function_file_test11: ################################################################################
misc/check_error.function_file_test11: 
misc/check_error.function_file_test11: Unable to match the following pattern against the program's output:
misc/check_error.function_file_test11: 
misc/check_error.function_file_test11: In \S+: Read more than two columns of data from file '\S+'.  Did you mean to use "format = rows" or set "xy_in_file_only" to false?
misc/check_error.function_file_test11: 
misc/check_error.function_file_test11: ################################################################################
misc/check_error.function_file_test11: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.function_file_test11: 
misc/check_error.function_file_test11 ........................................ FAILED (EXPECTED ERROR MISSING)
misc/check_error.coupled_nodal_for_non_nodal_variable: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.coupled_nodal_for_non_nodal_variable: Running command: /Users/me/projects/moose/test/moose_test-opt -i coupled_nodal_for_non_nodal_variable.i --error --error-override --libtorch-device cpu
misc/check_error.coupled_nodal_for_non_nodal_variable: ################################################################################
misc/check_error.coupled_nodal_for_non_nodal_variable: 
misc/check_error.coupled_nodal_for_non_nodal_variable: Unable to match the following pattern against the program's output:
misc/check_error.coupled_nodal_for_non_nodal_variable: 
misc/check_error.coupled_nodal_for_non_nodal_variable: m: Trying to get nodal values of variable 'v', but it is not nodal.
misc/check_error.coupled_nodal_for_non_nodal_variable: 
misc/check_error.coupled_nodal_for_non_nodal_variable: ################################################################################
misc/check_error.coupled_nodal_for_non_nodal_variable: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.coupled_nodal_for_non_nodal_variable: 
misc/check_error.coupled_nodal_for_non_nodal_variable ........................ FAILED (EXPECTED ERROR MISSING)
misc/check_error.bad_stateful_material_only_older: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.bad_stateful_material_only_older: Running command: /Users/me/projects/moose/test/moose_test-opt -i bad_stateful_material.i Materials/stateful_mat/get_older=true --error --error-override --libtorch-device cpu
misc/check_error.bad_stateful_material_only_older: ################################################################################
misc/check_error.bad_stateful_material_only_older: 
misc/check_error.bad_stateful_material_only_older: Unable to match the following pattern against the program's output:
misc/check_error.bad_stateful_material_only_older: 
misc/check_error.bad_stateful_material_only_older: One or more Material Properties were not supplied on block
misc/check_error.bad_stateful_material_only_older: 
misc/check_error.bad_stateful_material_only_older: ################################################################################
misc/check_error.bad_stateful_material_only_older: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.bad_stateful_material_only_older: 
misc/check_error.bad_stateful_material_only_older ............................ FAILED (EXPECTED ERROR MISSING)
misc/check_error.incomplete_fvkernel_variable_coverage_test: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.incomplete_fvkernel_variable_coverage_test: Running command: /Users/me/projects/moose/test/moose_test-opt -i incomplete_fvkernel_variable_coverage_test.i --error --error-override --libtorch-device cpu
misc/check_error.incomplete_fvkernel_variable_coverage_test: ################################################################################
misc/check_error.incomplete_fvkernel_variable_coverage_test: 
misc/check_error.incomplete_fvkernel_variable_coverage_test: Unable to match the following pattern against the program's output:
misc/check_error.incomplete_fvkernel_variable_coverage_test: 
misc/check_error.incomplete_fvkernel_variable_coverage_test: The following variable\(s\) lack an active kernel:
misc/check_error.incomplete_fvkernel_variable_coverage_test: 
misc/check_error.incomplete_fvkernel_variable_coverage_test: ################################################################################
misc/check_error.incomplete_fvkernel_variable_coverage_test: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.incomplete_fvkernel_variable_coverage_test: 
misc/check_error.incomplete_fvkernel_variable_coverage_test .................. FAILED (EXPECTED ERROR MISSING)
misc/check_error.bad_number: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.bad_number: Running command: /Users/me/projects/moose/test/moose_test-opt -i bad_number.i --error --error-override --libtorch-device cpu
misc/check_error.bad_number: ################################################################################
misc/check_error.bad_number: 
misc/check_error.bad_number: Unable to match the following pattern against the program's output:
misc/check_error.bad_number: 
misc/check_error.bad_number: invalid float syntax for parameter: BCs/right/value
misc/check_error.bad_number: 
misc/check_error.bad_number: ################################################################################
misc/check_error.bad_number: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.bad_number: 
misc/check_error.bad_number .................................................. FAILED (EXPECTED ERROR MISSING)
misc/check_error.add_aux_scalar_variable_multiple_test: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.add_aux_scalar_variable_multiple_test: Running command: /Users/me/projects/moose/test/moose_test-opt -i add_aux_variable_multiple_test.i Variables/q/family=SCALAR MoreAuxVariables/q/family=SCALAR --error --error-override --libtorch-device cpu
misc/check_error.add_aux_scalar_variable_multiple_test: ################################################################################
misc/check_error.add_aux_scalar_variable_multiple_test: 
misc/check_error.add_aux_scalar_variable_multiple_test: Unable to match the following pattern against the program's output:
misc/check_error.add_aux_scalar_variable_multiple_test: 
misc/check_error.add_aux_scalar_variable_multiple_test: AuxVariable with name 'q' already exists but is of a differing type!
misc/check_error.add_aux_scalar_variable_multiple_test: 
misc/check_error.add_aux_scalar_variable_multiple_test: ################################################################################
misc/check_error.add_aux_scalar_variable_multiple_test: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.add_aux_scalar_variable_multiple_test: 
misc/check_error.add_aux_scalar_variable_multiple_test ....................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.nan_no_trap_fpe_test_trans: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.nan_no_trap_fpe_test_trans: Running command: /Users/me/projects/moose/test/moose_test-opt -i nan_test_transient.i --no-trap-fpe --error --error-override --libtorch-device cpu
misc/check_error.nan_no_trap_fpe_test_trans: ################################################################################
misc/check_error.nan_no_trap_fpe_test_trans: 
misc/check_error.nan_no_trap_fpe_test_trans: Unable to match the following pattern against the program's output:
misc/check_error.nan_no_trap_fpe_test_trans: 
misc/check_error.nan_no_trap_fpe_test_trans: Solve Did NOT Converge
misc/check_error.nan_no_trap_fpe_test_trans: 
misc/check_error.nan_no_trap_fpe_test_trans: ################################################################################
misc/check_error.nan_no_trap_fpe_test_trans: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.nan_no_trap_fpe_test_trans: 
misc/check_error.nan_no_trap_fpe_test_trans .................................. FAILED (EXPECTED ERROR MISSING)
misc/check_error.scalar_kernel_with_var: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.scalar_kernel_with_var: Running command: /Users/me/projects/moose/test/moose_test-opt -i scalar_kernel_with_var.i --error --error-override --libtorch-device cpu
misc/check_error.scalar_kernel_with_var: ################################################################################
misc/check_error.scalar_kernel_with_var: 
misc/check_error.scalar_kernel_with_var: Unable to match the following pattern against the program's output:
misc/check_error.scalar_kernel_with_var: 
misc/check_error.scalar_kernel_with_var: Scalar variable 'u' does not exist in this system
misc/check_error.scalar_kernel_with_var: 
misc/check_error.scalar_kernel_with_var: ################################################################################
misc/check_error.scalar_kernel_with_var: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.scalar_kernel_with_var: 
misc/check_error.scalar_kernel_with_var ...................................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.deprecated_block_test: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.deprecated_block_test: Running command: /Users/me/projects/moose/test/moose_test-opt -i deprecated_block_test.i --error --error-override --libtorch-device cpu
misc/check_error.deprecated_block_test: ################################################################################
misc/check_error.deprecated_block_test: 
misc/check_error.deprecated_block_test: Unable to match the following pattern against the program's output:
misc/check_error.deprecated_block_test: 
misc/check_error.deprecated_block_test: Input file block '\S+' has been deprecated.
misc/check_error.deprecated_block_test: 
misc/check_error.deprecated_block_test: ################################################################################
misc/check_error.deprecated_block_test: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.deprecated_block_test: 
misc/check_error.deprecated_block_test ....................................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.unused_param_test_warn_cli: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.unused_param_test_warn_cli: Running command: /Users/me/projects/moose/test/moose_test-opt -i unused_param_test.i --allow-unused --error --error-override --libtorch-device cpu
misc/check_error.unused_param_test_warn_cli: ################################################################################
misc/check_error.unused_param_test_warn_cli: 
misc/check_error.unused_param_test_warn_cli: Unable to match the following pattern against the program's output:
misc/check_error.unused_param_test_warn_cli: 
misc/check_error.unused_param_test_warn_cli: unused parameter 'Mesh/unused_param'
misc/check_error.unused_param_test_warn_cli: 
misc/check_error.unused_param_test_warn_cli: ################################################################################
misc/check_error.unused_param_test_warn_cli: Tester failed, reason: EXPECTED OUTPUT MISSING
misc/check_error.unused_param_test_warn_cli: 
misc/check_error.unused_param_test_warn_cli ................................. FAILED (EXPECTED OUTPUT MISSING)
misc/check_error.function_file_test2: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.function_file_test2: Running command: /Users/me/projects/moose/test/moose_test-opt -i function_file_test2.i --error --error-override --libtorch-device cpu
misc/check_error.function_file_test2: ################################################################################
misc/check_error.function_file_test2: 
misc/check_error.function_file_test2: Unable to match the following pattern against the program's output:
misc/check_error.function_file_test2: 
misc/check_error.function_file_test2: In \S+: Read more than two columns of data from file '\S+'.  Did you mean to use "format = rows"?
misc/check_error.function_file_test2: 
misc/check_error.function_file_test2: ################################################################################
misc/check_error.function_file_test2: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.function_file_test2: 
misc/check_error.function_file_test2 ......................................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.scalar_old_integrity_check: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.scalar_old_integrity_check: Running command: /Users/me/projects/moose/test/moose_test-opt -i scalar_old_integrity_check.i --error --error-override --libtorch-device cpu
misc/check_error.scalar_old_integrity_check: ################################################################################
misc/check_error.scalar_old_integrity_check: 
misc/check_error.scalar_old_integrity_check: Unable to match the following pattern against the program's output:
misc/check_error.scalar_old_integrity_check: 
misc/check_error.scalar_old_integrity_check: Calling 'coupledScalarValueOld' on variable \S+ when using a \"Steady\" executioner is not allowed. This value is available only in transient simulations.
misc/check_error.scalar_old_integrity_check: 
misc/check_error.scalar_old_integrity_check: ################################################################################
misc/check_error.scalar_old_integrity_check: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.scalar_old_integrity_check: 
misc/check_error.scalar_old_integrity_check .................................. FAILED (EXPECTED ERROR MISSING)
misc/check_error.coupled_nodal_for_non_nodal_variable_old: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.coupled_nodal_for_non_nodal_variable_old: Running command: /Users/me/projects/moose/test/moose_test-opt -i coupled_nodal_for_non_nodal_variable.i Materials/m/lag=OLD --error --error-override --libtorch-device cpu
misc/check_error.coupled_nodal_for_non_nodal_variable_old: ################################################################################
misc/check_error.coupled_nodal_for_non_nodal_variable_old: 
misc/check_error.coupled_nodal_for_non_nodal_variable_old: Unable to match the following pattern against the program's output:
misc/check_error.coupled_nodal_for_non_nodal_variable_old: 
misc/check_error.coupled_nodal_for_non_nodal_variable_old: m: Trying to get old nodal values of variable 'v', but it is not nodal.
misc/check_error.coupled_nodal_for_non_nodal_variable_old: 
misc/check_error.coupled_nodal_for_non_nodal_variable_old: ################################################################################
misc/check_error.coupled_nodal_for_non_nodal_variable_old: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.coupled_nodal_for_non_nodal_variable_old: 
misc/check_error.coupled_nodal_for_non_nodal_variable_old .................... FAILED (EXPECTED ERROR MISSING)
misc/check_error.function_file_test12: Working Directory: /Users/me/projects/moose/test/tests/misc/check_error
misc/check_error.function_file_test12: Running command: /Users/me/projects/moose/test/moose_test-opt -i function_file_test12.i --error --error-override --libtorch-device cpu
misc/check_error.function_file_test12: ################################################################################
misc/check_error.function_file_test12: 
misc/check_error.function_file_test12: Unable to match the following pattern against the program's output:
misc/check_error.function_file_test12: 
misc/check_error.function_file_test12: Index out-of-range of the available data in '\S+', which contains 3 columns of data.
misc/check_error.function_file_test12: 
misc/check_error.function_file_test12: ################################################################################
misc/check_error.function_file_test12: Tester failed, reason: EXPECTED ERROR MISSING
misc/check_error.function_file_test12: 
misc/check_error.function_file_test12 ........................................ FAILED (EXPECTED ERROR MISSING)

Encountering Errors? Please include diagnostic output

No response

Answered by GiudGiud

Aug 24, 2024

The executable does not build. Probably because moose is relying on libmesh features that are only present in newer versions of the package.

So we are toast with current moose.

You ll need to check out a version of moose from mid July as well. That one will build with libmesh from mid July

View full answer

GiudGiud · 2024-08-23T14:30:32Z

GiudGiud
Aug 23, 2024
Collaborator

Hello

Could you please go in test/tests/kernels/simple_diffusion and run that test (using the executable in moose/test) and report the full log?

Thanks
Guillaume

11 replies

frankwugeo Aug 23, 2024
Author

I tried uninstall and use the previous version as

conda create -n moose moose-dev=2024.07.15 mpich

However, the tests still report similar (a lot) errors related to the 'misc/check_error'

GiudGiud Aug 23, 2024
Collaborator

Did it build well the second time?

What does it do in the simple_diffusion folder again?

frankwugeo Aug 24, 2024
Author

An error occurs when I make again.

In file included from /Users/me/projects/moose/framework/build/unity_src/systems_Unity.C:10:
/Users/me/projects/moose/framework/src/systems/NonlinearEigenSystem.C:284:34: error: no viable conversion from '__libcpp_remove_reference_t<unique_ptr<NumericVector<double>, default_delete<NumericVector<double>>> &>' (aka 'std::unique_ptr<libMesh::NumericVector<double>>') to 'NumericVector<double>'
    solution().restore_subvector(std::move(subvec), _eigen_sys.local_non_condensed_dofs_vector);
                                 ^~~~~~~~~~~~~~~~~
/Users/me/miniconda3/envs/moose/libmesh/include/libmesh/numeric_vector.h:126:3: note: candidate constructor not viable: no known conversion from '__libcpp_remove_reference_t<unique_ptr<NumericVector<double>, default_delete<NumericVector<double>>> &>' (aka 'std::unique_ptr<libMesh::NumericVector<double>>') to 'const NumericVector<double> &' for 1st argument
  NumericVector (const NumericVector &) = default;
  ^
/Users/me/miniconda3/envs/moose/libmesh/include/libmesh/numeric_vector.h:77:3: note: explicit constructor is not a candidate
  NumericVector (const Parallel::Communicator & comm_in,
  ^
/Users/me/miniconda3/envs/moose/libmesh/include/libmesh/numeric_vector.h:748:53: note: passing argument to parameter here
  virtual void restore_subvector(NumericVector<T> &&, const std::vector<numeric_index_type> &)
                                                    ^
Compiling C++ (in opt mode) /Users/me/projects/moose/framework/build/unity_src/fviks_Unity.C...
Compiling C++ (in opt mode) /Users/me/projects/moose/framework/build/unity_src/ics_Unity.C...
Compiling C++ (in opt mode) /Users/me/projects/moose/framework/build/unity_src/linearfvbcs_Unity.C...
1 error generated.
make: *** [/Users/me/projects/moose/framework/build.mk:151: /Users/me/projects/moose/framework/build/unity_src/systems_Unity.x86_64-apple-darwin13.4.0.opt.lo] Error 1
make: *** Waiting for unfinished jobs....

For the simple diffusion test, I do not find the exec 'moose_test-opt' in moose/test file this time.

zsh: no such file or directory: ../../../moose_test-opt

GiudGiud Aug 24, 2024
Collaborator

The executable does not build. Probably because moose is relying on libmesh features that are only present in newer versions of the package.

So we are toast with current moose.

You ll need to check out a version of moose from mid July as well. That one will build with libmesh from mid July

Answer selected by frankwugeo

milljm Aug 26, 2024
Maintainer

Linking with #28340 to keep track.

frankwugeo Aug 26, 2024
Author

It's finally working by installing the version of 07.19. Almost all tests passed and the simple diffusion case also worked well.

conda create -n moose moose-dev=2024.07.19 mpich

Also, be reminded to clean the build before 'make'

cd moose
git clean -xfd; git submodule foreach --recursive git clean -xfd

Thank you for your time, Guillaume @GiudGiud and @milljm.

milljm Aug 26, 2024
Maintainer

Dang... I mean, I am glade its working, but this whole "install an older package" thing is certainly not the solution.

milljm Aug 28, 2024
Maintainer

We're identifying the issue: #28484

EdSheltonUKAEA · 2024-09-03T10:15:21Z

EdSheltonUKAEA
Sep 3, 2024

I think I've got a problem related to this having tried to do a conda and moose update.
I proceeded as normal and got an error while running make and failure running tests.
I had a look on the forum and found this issue, related threads and what looks like the recent change to the "new users - staying up-to-date" advice (https://mooseframework.inl.gov/getting_started/new_users.html). So I have tried to apply the fixes here.

Now I seem to have removed moose with
conda env remove -n moose
but can't reinstall either the 2024.08.26 or 2024.07.19 versions using the commands:
conda create -n moose moose-dev=2024.08.26 mpich
conda create -n moose moose-dev=2024.07.19 mpich

I'm trying to do this from "base" in conda. I get these messages and then the installation just hangs. I left it overnight for 12+ hours and nothing happened. It's just sat there waiting to collect a package.
(base) timodel01@M0239:~$ conda create -n moose moose-dev=2024.08.26 mpich
Collecting package metadata (current_repodata.json): done
Solving environment: unsuccessful attempt using repodata from current_repodata.json, retrying with next repodata source.
Collecting package metadata (repodata.json): /

How can I expedite the package delivery?

8 replies

GiudGiud Sep 3, 2024
Collaborator

updating conda further wont hurt

Is the current recommendation to update moose with the 2024.08.26 or 2024.07.19 version?

some machines are affected by an "illegal instruction" error with the latest version. If your machine is brand new you can try the latest.
Rolling back both moose-libmesh and your local version of moose to mid-July will work for older and newer machines

EdSheltonUKAEA Sep 3, 2024

I tried the conda update, but it just repeats the same warning that a newer version exists. It doesn't seem to update with the newer vesion.

As I'm using an older machine with existing installations I've tried again with the July version:

conda create -n moose moose-dev=2024.07.19 mpich

It's now got a step further. The first attempt at collecting package metadata is "done". But then solving environment is unsucessful with the repodata. However the second collecting of repodata now worked but it's hung on solving environment for this.
Prompted by your comment above on conda being slow, and from a bit of googling, I see this is not unusual. To get this to work quicker, could I retry with mamba, or is there a way I can force conda to update to version 24.7.1?

GiudGiud Sep 3, 2024
Collaborator

so this does not work?
conda install conda=24.7.1

You can try with mamba if you would like
it's just conda install mamba then open a new tab then mamba install ...

note that sometimes it s easier to remove the miniconda/miniforge directory and re-download everything from this page
https://mooseframework.inl.gov/getting_started/installation/conda.html
It mostly removes any long dependency solve

milljm Sep 3, 2024
Maintainer

There is sometimes not an update path forward available for your installation of Conda. I have found this to be the case in the most recent upgrade process (from 23 to 24).

The solution in this case is to completely delete your current installation of Conda and install anew:

rm -rf ~/miniforge

# Linux
# curl -L -O https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh

# Intel Mac
#curl -L -O https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-MacOSX-x86_64.sh

# Apple Si Mac
# curl -L -O https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-MacOSX-arm64.sh

bash Miniforge3-the-thing-you-downloaded-above -b -p ~/miniforge
exit

And then re-open your terminal window(s). No need to run conda init routines as those functions are already present in your shell profile.

At this point, it doesn't hurt to perform an update in the base environment:

conda activate base
conda update --all --yes

Finally, you should be able to install (quickly) the desired Conda packages.

We're still working on getting the "Illegal Instruction" issue solved...

EdSheltonUKAEA Sep 3, 2024

That's fixed it! New conda installation. Moose reinstalled using latest August version with no errors and test passed. My application updated and now running a model. (Sort of - it isn't coverging, but fixing that is something I can try to sort out myself.)
Thank you so much!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MOOSE install: successful build, but got failed tests #28461

{{title}}

Replies: 2 comments 19 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

MOOSE install: successful build, but got failed tests #28461

frankwugeo Aug 23, 2024

Check these boxes if you have followed the posting rules.

Issue or question about MOOSE

(Optional) code in question / simulation log / errors

Encountering Errors? Please include diagnostic output

Replies: 2 comments · 19 replies

GiudGiud Aug 23, 2024 Collaborator

frankwugeo Aug 23, 2024 Author

GiudGiud Aug 23, 2024 Collaborator

frankwugeo Aug 24, 2024 Author

GiudGiud Aug 24, 2024 Collaborator

milljm Aug 26, 2024 Maintainer

frankwugeo Aug 26, 2024 Author

milljm Aug 26, 2024 Maintainer

milljm Aug 28, 2024 Maintainer

EdSheltonUKAEA Sep 3, 2024

GiudGiud Sep 3, 2024 Collaborator

EdSheltonUKAEA Sep 3, 2024

GiudGiud Sep 3, 2024 Collaborator

milljm Sep 3, 2024 Maintainer

EdSheltonUKAEA Sep 3, 2024

frankwugeo
Aug 23, 2024

Replies: 2 comments 19 replies

GiudGiud
Aug 23, 2024
Collaborator

frankwugeo Aug 23, 2024
Author

GiudGiud Aug 23, 2024
Collaborator

frankwugeo Aug 24, 2024
Author

GiudGiud Aug 24, 2024
Collaborator

milljm Aug 26, 2024
Maintainer

frankwugeo Aug 26, 2024
Author

milljm Aug 26, 2024
Maintainer

milljm Aug 28, 2024
Maintainer

EdSheltonUKAEA
Sep 3, 2024

GiudGiud Sep 3, 2024
Collaborator

GiudGiud Sep 3, 2024
Collaborator

milljm Sep 3, 2024
Maintainer