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
I've seen the same error happen with two of the tests, test_coupler.sh test 3 and test_data_override2_mono.sh test 1.
To Reproduce
compile with gcc 13 and debug flags (-O0 -fbacktrace -fbounds-check -fbacktrace -ffpe-trap=invalid,zero,overflow), then run either the coupler or data_override tests a couple of times until it comes up.
Expected behavior
Not fail, all tests should be pass with debug flags.
System Environment
amd box with gcc 13.3.0 + mpich.
Additional context
This is preventing #1579 from working. On the amd box these error don't happen every run, but in the ci it seems to fail every time (maybe due to it running 7 different instances, one failure is bound to happen).
field%src_data is a pointer, and hi_tmp_src_data is an allocatable, so that likely has something to do with it.
The text was updated successfully, but these errors were encountered:
Describe the bug
Occasionally on the amd box and in the ci, this line generates a floating point exception:
FMS/time_interp/time_interp_external2.F90
Line 857 in d13c129
I've seen the same error happen with two of the tests,
test_coupler.sh
test 3 andtest_data_override2_mono.sh
test 1.To Reproduce
compile with gcc 13 and debug flags (
-O0 -fbacktrace -fbounds-check -fbacktrace -ffpe-trap=invalid,zero,overflow
), then run either the coupler or data_override tests a couple of times until it comes up.Expected behavior
Not fail, all tests should be pass with debug flags.
System Environment
amd box with gcc 13.3.0 + mpich.
Additional context
This is preventing #1579 from working. On the amd box these error don't happen every run, but in the ci it seems to fail every time (maybe due to it running 7 different instances, one failure is bound to happen).
field%src_data
is a pointer, andhi_tmp_src_data
is an allocatable, so that likely has something to do with it.The text was updated successfully, but these errors were encountered: