Bug Description
Based on guidance in the 2021-11 MOOSE newsletter, I tried to update the MOOSE environment on our ORNL machines. The process consistently failed to update the moose-libmesh and moose-tools libraries (no matter how much I tried to manually force it to install certain versions, conda kept claiming that it was already installed). I finally wiped the environment and started from scratch following the MOOSE "getting started" instructions.
For my normal development setup, this worked fine. However, the CI we have for our Mole code is failing with the following errors during compilation:
Compiling C++ (in opt mode) /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/build/unity_src/kernels_Unity.C...
Compiling C++ (in opt mode) /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/build/unity_src/materials_Unity.C...
Compiling C++ (in opt mode) /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/build/unity_src/postprocessors_Unity.C...
Compiling C++ (in opt mode) /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/build/unity_src/utils_Unity.C...
Linking Library /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/moose/modules/chemical_reactions/lib/libchemical_reactions-opt.la...
Linking Library /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/moose/modules/module_loader/lib/libmodule_loader_with_cr_ls-opt.la...
Linking Library /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/test/lib/libmole_test-opt.la...
Linking Library /localhome/gitlab-runner/builds/43d03e71/0/mole/mole/moose/framework/libmoose-opt.la...
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkIOCore-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkCommonCore-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkCommonDataModel-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkFiltersCore-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkIOXML-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkImagingCore-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkIOImage-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkImagingMath-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkIOParallelXML-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkParallelMPI-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkParallelCore-6.3
/localhome/gitlab-runner/miniconda3/envs/moose/bin/../lib/gcc/x86_64-conda-linux-gnu/9.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: cannot find -lvtkCommonExecutionModel-6.3
collect2: error: ld returned 1 exit status
make: *** [/localhome/gitlab-runner/builds/43d03e71/0/mole/mole/moose/framework/libmoose-opt.la] Error 1
make: *** Waiting for unfinished jobs....
Steps to Reproduce
It is unclear how to reproduce this since I did the same process one several different machines. MOOSE builds fine on my normal development machine (where I am manually building it), but it fails to build on the CI machine (where the build process is automated but follows the same set of commands as what I would do manually).
Impact
It prevents our automated testing from working properly, which is requirement to accept changes to Mole. We can manually test everything and post results but that's a nuisance and is definitely not as good of a QA procedure.
Bug Description
Based on guidance in the 2021-11 MOOSE newsletter, I tried to update the MOOSE environment on our ORNL machines. The process consistently failed to update the moose-libmesh and moose-tools libraries (no matter how much I tried to manually force it to install certain versions, conda kept claiming that it was already installed). I finally wiped the environment and started from scratch following the MOOSE "getting started" instructions.
For my normal development setup, this worked fine. However, the CI we have for our Mole code is failing with the following errors during compilation:
Steps to Reproduce
It is unclear how to reproduce this since I did the same process one several different machines. MOOSE builds fine on my normal development machine (where I am manually building it), but it fails to build on the CI machine (where the build process is automated but follows the same set of commands as what I would do manually).
Impact
It prevents our automated testing from working properly, which is requirement to accept changes to Mole. We can manually test everything and post results but that's a nuisance and is definitely not as good of a QA procedure.