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
Amazingly the GCC14-NoMPI-Complex-Mixed-Debug run of short-diamondC_1x1x1_pp-dmc_sdj-1-16 ( https://cdash.qmcpack.org/tests/4312408 ) is giving an assertion failure indicating a bad index, and subsequently aborting. It is the only configuration for this test currently giving an error -- the other real/mixed/complex debug builds do not abort.
@ye-luo Can you please take a look at this? I wonder how this is logically possible. Perhaps we have a <= when we need a < somewhere, or variation in how the pbc is done allowing for numerical error? Happy to instrument this run and do more testing of it.
Describe the bug
Amazingly the GCC14-NoMPI-Complex-Mixed-Debug run of short-diamondC_1x1x1_pp-dmc_sdj-1-16 ( https://cdash.qmcpack.org/tests/4312408 ) is giving an assertion failure indicating a bad index, and subsequently aborting. It is the only configuration for this test currently giving an error -- the other real/mixed/complex debug builds do not abort.
qmcpack_complex: /scratch/pk7/QMCPACK_CI_BUILDS/qmcpack/src/einspline/bspline_eval_d_std.cpp:39: void coeff_offset_UBspline_d(const Ugrid*, const BCtype_d*, double, int&, double&): Assertion `ipart <= grid->num -1' failed.
To Reproduce
Nightly run configuration, develop version, ctest -R short-diamondC_1x1x1_pp-dmc_sdj-1-16
Expected behavior
Test passes
System:
nitrogen2, nightly configuration
Additional context
??!!!
The text was updated successfully, but these errors were encountered: