Phantom PR for libMesh testing purposes only 👻 🎃 #28969
Conversation
libmesh
Outdated
| @@ -1 +1 @@ | |||
| Subproject commit 5483644b60cc538a4b54d312f28835bd94107627 | |||
| Subproject commit 0bb27d899eb85639516e1db96ae2e5810e90f09c | |||
There was a problem hiding this comment.
Caution! This contains a submodule update
|
Job Precheck, step Conda libmesh build config check on d629cca wanted to post the following: A change of the following file(s) triggered this check: libmesh The following file(s) are unchanged: conda/mpi/conda_build_config.yaml The libmesh submodule or configuration was changed but the conda build config was not |
|
Job Documentation, step Docs: sync website on 4afe418 wanted to post the following: View the site here This comment will be updated on new commits. |
|
Job Coverage, step Generate coverage on 4afe418 wanted to post the following: Framework coverage
Modules coverageCoverage did not change Full coverage reportsReports
This comment will be updated on new commits. |
||||||||||||||||||||||||||
libmesh
Outdated
| @@ -1 +1 @@ | |||
| Subproject commit 5483644b60cc538a4b54d312f28835bd94107627 | |||
| Subproject commit b5e429808dddfa2d1fb824ebe799cdb2a89a0262 | |||
There was a problem hiding this comment.
Caution! This contains a submodule update
|
Job Precheck, step Conda libmesh build config check on 35c1762 wanted to post the following: A change of the following file(s) triggered this check: libmesh The following file(s) are unchanged: conda/mpi/conda_build_config.yaml The libmesh submodule or configuration was changed but the conda build config was not |
|
Ah, of course, can't touch @lindsayad, @roystgnr, can one of you create a branch in libMesh/libmesh pointing to farscape-project/libmesh:workaround (libMesh/libmesh#3984)? |
libmesh
Outdated
| @@ -1 +1 @@ | |||
| Subproject commit 5483644b60cc538a4b54d312f28835bd94107627 | |||
| Subproject commit b5e429808dddfa2d1fb824ebe799cdb2a89a0262 | |||
There was a problem hiding this comment.
Caution! This contains a submodule update
|
Job Precheck, step Conda libmesh build config check on a1aee42 wanted to post the following: A change of the following file(s) triggered this check: libmesh The following file(s) are unchanged: conda/mpi/conda_build_config.yaml The libmesh submodule or configuration was changed but the conda build config was not |
| @@ -1 +1 @@ | |||
| Subproject commit 5483644b60cc538a4b54d312f28835bd94107627 | |||
| Subproject commit 8b482a9bbdf752908cb374c7f800d7dc326afca4 | |||
There was a problem hiding this comment.
Caution! This contains a submodule update
|
Job Precheck, step Conda libmesh build config check on 4afe418 wanted to post the following: A change of the following file(s) triggered this check: libmesh The following file(s) are unchanged: conda/mpi/conda_build_config.yaml The libmesh submodule or configuration was changed but the conda build config was not |
|
@lindsayad It seems Griffin doesn't like your static condensation additions/changes to libMesh, so that'll need looking into :/ |
|
Ok I will look into it soon |
Never to be merged.
Step 1: Confirm only MOOSE controlled/internal apps tests fail with the most current version of libMesh. ✅
Step 2: Add a workaround in libMesh "to establish more backwards compatibility so that we can keep CI green while we update subchannel and other apps" as originally requested by @lindsayad in #28929 (comment).