You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens somewhat regularly on my PR (AFAIK this is not introduced with my changes), but at least the latest run on develop is OK.
Error message:
462/639 Test #462: vt:TestMpiAccessGuardDeathTest.test_mpi_access_prevented_proc_2 ....................***Failed Error regular expression found in output. Regex=[Segmentation fault] 0.22 sec
Note: Google Test filter = TestMpiAccessGuardDeathTest.test_mpi_access_prevented
[==========] Running 1 test from 1 test suite.
(...)
vt: [1] ------------------------------------------------------------------------------------------------------------------------
vt: [1] ------------------------------------------- Runtime Error: System Aborting! --------------------------------------------
vt: [1] ------------------------------------------------ Fatal Error on Node 1 -------------------------------------------------
vt: [1] ------------------------------------------------------------------------------------------------------------------------
vt: [1]
vt: [1] Message: FATAL ERROR: The MPI function 'MPI_Test' was called from a VT handler. MPI functions should not used inside user code invoked from VT handlers.
vt: [1]
vt: Caught SIGSEGV signal: 11
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 6687 RUNNING AT d6708d320b27
= EXIT CODE: 139
(...)
This happens somewhat regularly on my PR (AFAIK this is not introduced with my changes), but at least the latest run on
develop
is OK.Error message:
See the detailed logs: https://dev.azure.com/DARMA-tasking/DARMA/_build/results?buildId=26333&view=logs&j=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3&t=28db5144-7e5d-5c90-2820-8676d630d9d2
Marking as low priority since this is Alpine build (which we might remove / replace with CentOS-like build).
The text was updated successfully, but these errors were encountered: