I have made it through the entire build process, but when I go to run the ctest from the build/mpas-jedi, the three geometry tests (2:test_mpasjedi_geometry, 8:test_mpasjedi_geometry_iterator_2d_2pe, 9:test_mpasjedi_geometry_iterator_3d_2pe) fail in the same manner:
OOPS Starting 2025-12-15 19:49:06 (UTC+0000)
Configuration input file is: testinput/geometry.yaml
Full configuration is:YAMLConfiguration[path=testinput/geometry.yaml, root={geometry => {nml_file => ./Data/480km/namelist.atmosphere_2018041500 , streams_file => ./Data/480km/streams.atmosphere , deallocate non-da fields => true , gmsh_save => true , gmsh_filename => ./global480km.msh}}]
OOPS_STATS ObjectCountHelper started.
OOPS_STATS Run start - Runtime: 0.05 sec, Memory: total: 53.02 Mb, per task: min = 53.02 Mb, max = 53.02 Mb
Run: Starting oops::Test running test::Geometry<MPAS>
Running 2 tests:
Running case 0: interface/Geometry/testConstructor ...
==> create geom
Testing geometry: , nCellsGlobal = 2562, nCells = 2562, nCellsSolve = 2562, nEdgesGlobal = 7680, nEdges = 7680, nEdgesSolve = 7680, nVertLevels = 6, nVertLevelsP1 = 7, communicator = world
==> destruct MPAS corelist and domain: 0
Completed case 0: interface/Geometry/testConstructor
Running case 1: interface/Geometry/testAtlasInterface ...
==> create geom
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object being used after deletion - Bad Object
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object being used after deletion - Internal subroutine call returned Error
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Wrong argument specified - , need real calendar.
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Wrong argument specified - Internal subroutine call returned Error
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Wrong argument specified - Internal subroutine call returned Error
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object being used before creation - Bad Object
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
ESMF_LogWrite(): ESMF_Log not open -- cannot ESMF_LogWrite(). Log message = Object Set or SetDefault method not called - Object not Initialized
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
Proc: [[11940,1],0]
Errorcode: 1734831948
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
prterun has exited due to process rank 0 with PID 0 on node orion-devel-1 calling
"abort". This may have caused other processes in the application to be
terminated by signals sent by prterun (as reported here).
--------------------------------------------------------------------------
<end of output>
Test time = 1.04 sec
----------------------------------------------------------
Test Failed.
"test_mpasjedi_geometry" end time: Dec 15 19:49 UTC
"test_mpasjedi_geometry" time elapsed: 00:00:01
----------------------------------------------------------
I also found the following in the /build/mpas-jedi/test/log.atmosphere.0000.d0001.err file.
----------------------------------------------------------------------
Beginning MPAS-atmosphere Error Log File for task 0 of 1
for domain ID 1
Opened at 2025/12/15 19:49:06
----------------------------------------------------------------------
ERROR: Invalid DateTime string (invalid time substring) initial_time
CRITICAL ERROR: Could not open input file './Data/480km/bg/restart.0000-32765-00_22016.403359596.00.nc' to read mesh fields
Logging complete. Closing file at 2025/12/15 19:49:06
I used the jedi container and sourced /opt/spack-environment/activate.sh to set up the environment. I checked the data files and confirmed that they are in that location. I am missing something with the environment that would correct this issue?