Update packages#32757
Conversation
|
Job Documentation, step Docs: sync website on dab3bad wanted to post the following: View the site here This comment will be updated on new commits. |
|
@lindsayad Can we make sure your MetaPhysicL fix will be in with this update? |
214c9c3 to
d0b39a6
Compare
sounds good |
bd0620d to
31b2ecc
Compare
590522f to
be31d30
Compare
4604f4f to
69c6a60
Compare
ec0df19 to
5cf5eee
Compare
|
What's the ETA of this? If it will take a few more days, can we include a small libMesh bug fix that Roy will make today or tomorrow? |
We'll see. Because @roystgnr went on a unit test fix rampage I'm not sure if it'll be ready in time |
This reverts commit d908ec3. refs idaholab#32757
…cks missing libnvidia-ml.so.1 For SLATE and netCDF we leverage the fact that the simple programs that CMake and autotools use to test the compilers do not actually need libnvidia-ml.so, they are just linked against it because that is an inherited dependency from PETSc (as of 5268dc8a, !8817). We use -Wl,--as-needed to drop that dependency at compile time, so the dynamic linker does not complain at runtime. For MFEM, the check is on the PETSc library itself, which we know must be working correctly since, by the time we build MFEM, we have already compiled libMesh against PETSc. As PETSc does require libnvidia-ml.so.1, we bypass the test altogether with -DPETSC_EXECUTABLE_RUNS=YES. refs idaholab#32757
OpenBLAS uses a script, f_check, to determine what the Fortran compiler is. Problem is, with FC=mpif90, even though mpif90 wraps ifx, OpenBLAS makes a mess and assigns NOFORTRAN=1 and other flags relative to gfortran instead. The net effect is that PETSc's post-install checks hang. refs idaholab#32757
… petsc recipe The conda scalapack package's scalapack-targets.cmake embeds absolute CI build-machine paths (/opt/civet0/...) and GCC emulated-TLS libs (-lemutls_w, -lheapt_w) in INTERFACE_LINK_LIBRARIES. These propagate through MUMPS into MFEM's link libraries, causing fatal link errors on macOS Apple Silicon. Extend the existing Darwin GCC-stripping block to also cover scalapack-targets.cmake: add it to the existing sed for -lemutls_w/-lheapt_w/ -lgcc_s.1, and add a second sed to strip the -Wl,-rpath and -L flags pointing at /opt/civet0 (which don't appear in the PETSc files and so weren't handled before). refs idaholab#32757 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This is causing crashes on INL HPC and I will do it elsewhere refs idaholab#32757
This fixes conda activation when using sh instead of bash in Docker refs idaholab#32803
Summary of changes: - Improved Kokkos configuration and compatibility in MetaPhysicL - Updated ThreadedBuildingBlocks compatibility for modern oneTBB - Enabled future fine-grained control of subvector type in create_subvector() - Added Netgen control for tetrahedralization multithreading; set Netgen thread count to match libMesh n_threads - More robust build system behavior when rebuilding after Netgen updates - More assertions in AnalyticFunction - Fix for compiler warning in libMesh from OSX 26.4 - Fix for compiler warning in TIMPI - Clarification in TIMPI parallel sync documentation - `restrict_int<T>` can now be used in place of `cast_int<T>`, to enable integer conversion range checking in optimized modes, not just in devel and debug modes. - `restrict_int` is now used in many mesh input classes, to improve safety when libMesh builds with small `subdomain_id_type` configurations are asked to read mesh files with too-large subdomain ids. - `IntRange` (the output type of `make_range`) is now usable as a `Threads::` range - `NumericVector<T>::l2_norm_diff()` is now multithreaded - When building with `METHOD=oprof`, app binaries with `oprof` settings are now also built - Added `--enable-sigint` command-line option, telling libMesh applications to handle `SIGINT` (the Ctrl+C signal). The usual termination handler can then print stack trace and any incomplete `PerfLog` output, which can make threading and profiling easier when investigating application cases which run very long or hang entirely. refs idaholab#32757
|
Job Precheck, step Versioner verify on dab3bad wanted to post the following: Versioner templatesFound 11 templates, 0 failed Versioner influential filesFound 53 influential files, 14 changed, 0 added, 0 removed
Versioner versionsFound 10 packages, 3 changed, 0 failed
|
|
Job Test, step Results summary on dab3bad wanted to post the following: Framework test summaryCompared against 1ba05b6 in job civet.inl.gov/job/3806839. No change Modules test summaryCompared against 1ba05b6 in job civet.inl.gov/job/3806839. No change |
|
The libMesh bug fix was merged |
|
32bit dof ids failures will be skipped in #32897 |
libMesh update libMesh/libmesh@0185b8b...aeab0b9
IntRange(the output type ofmake_range) is now usable as aThreads::rangeNumericVector<T>::l2_norm_diff()is now multithreadedMETHOD=oprof, app binaries withoprofsettings are now also built--enable-sigintcommand-line option, telling libMesh applications to handleSIGINT(the Ctrl+C signal). The usual termination handler can then print stack trace and any incompletePerfLogoutput, which can make threading and profiling easier when investigating application cases which run very long or hang entirely.Conda packages
moose-petsc 3.25.1 [mpich,openmpi]_0v3.24.6..v3.25.1moose-libmesh 2026.05.06_aeab0b9 [mpich,openmpi]_0moose-petsc 3.25.1_0moose-dev 2026.05.08 [mpich,openmpi]moose-petsc 3.25.1 [mpich,openmpi]_0moose-libmesh 2026.05.06_aeab0b9 [mpich,openmpi]_0Apptainer containers
moose-petsc:3.25.1_0v3.24.6..v3.25.1libnvidia-ml.so.1by passing-DCMAKE_EXE_LINKER_FLAGS=-Wl,--as-neededto SLATE's CMake command to drop that library dependencyDYNAMIC_ARCH=1 NOFORTRAN=0 F_COMPILER=INTEL FEXTRALIB=to its make commandmoose-libmesh:2026.05.06_aeab0b9_0moose-petsc:3.25.1_0container as baselibnvidia-ml.so.1by passing-Wl,--as-neededto netCDF's configure command to drop that library dependencymoose-dev:2026.05.08moose-libmesh:2026.05.06_aeab0b9_0container as baselibnvidia-ml.so.1by passing-DPETSC_EXECUTABLE_RUNS=YESto MFEM's CMake command to ignore failing PETSc testscode-server-startwhich is causing issues on INL HPC