It would be useful if benchcab supported testing CABLE with debug builds and/or builds with configurable compiler flags so that we can catch any runtime exceptions or warnings that may be hidden in a release build (for example in https://github.com/CABLE-LSM/benchcab/issues/304 it would have been useful to catch the floating point overflow exception sooner).
It would be useful if benchcab supported testing CABLE with debug builds and/or builds with configurable compiler flags so that we can catch any runtime exceptions or warnings that may be hidden in a release build (for example in https://github.com/CABLE-LSM/benchcab/issues/304 it would have been useful to catch the floating point overflow exception sooner).
This functionality comes by default with a spack based workflow (https://github.com/CABLE-LSM/benchcab/issues/286).