Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

Authorization required, but no authorization protocol specified

There are more MPI processes than the number of unique GPU devices. This is not necessarily a problem.
For example this could happen when a device such as MI300A is partitioned into multiple subdevices.!
Should use 2-D Smagorinsky for mesoscale resolution!
Should use 2-D Smagorinsky for mesoscale resolution!
Should use 2-D Smagorinsky for mesoscale resolution!
Should use 2-D Smagorinsky for mesoscale resolution!
/home/regtester/git/amrex//Src/Base/AMReX.H:218: void amrex::Assert(const char *, const char *, int, const char *): block: [0,0,0], thread: [0,0,0] Assertion `0` failed.
amrex::Abort::2::CUDA error 710 in file /home/regtester/git/amrex//Src/Base/AMReX_GpuDevice.cpp line 184: device-side assert triggered !!!
SIGABRT
See Backtrace.2 file for details
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 2 in communicator MPI COMMUNICATOR 3 DUP FROM 0
with errorcode 6.

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.
--------------------------------------------------------------------------