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
f77/io/iwriteatallf intermittently fails due to stack fault on Jenkins. One failure example on clang,debug,ubuntu64 is like the following:
## Test output (expected 'No Errors'):
## Fatal error in MPI_Testall: Unknown error class, error stack:
## MPI_Testall(254)......................: MPI_Testall(count=2, req_array=0x23819f8, flag=0x7fff9e6950e0, status_array=0x1) failed
## MPIDI_CH3I_Progress(463)..............:
## MPIDU_Sched_progress_state(834).......:
## MPIDU_Complete_posted_with_error(1192): Process failed
##
## ==================================================================================# ##BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
## = PID 25797 RUNNING AT bb66
## = EXIT CODE: 16
## = CLEANING UP REMAINING PROCESSES
## = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
## ===================================================================================
## YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Stack fault (signal 16)
## This typically refers to a problem with your application.
## Please see the FAQ page for debugging suggestions
The text was updated successfully, but these errors were encountered:
This is currently a workaround to avoid weird errors, e.g., stack
fault, occurred in the NBC I/O implementation on Linux. When the host
OS is Linux and aio-lite is not used, a blocking ADIO function is used
in the NBC I/O implementation.
Originally by sseo on 2014-11-17 13:06:44 -0600
f77/io/iwriteatallf intermittently fails due to stack fault on Jenkins. One failure example on clang,debug,ubuntu64 is like the following:
The text was updated successfully, but these errors were encountered: