testtools fails with forced python interpreter
In order to debug python bindings I need to have the DUNE venv created with python3.7-dbg as the interpreter. I achieve this with passing -DPYTHON_EXECUTABLE=/usr/bin/python3.7-dbg thru the config opts. However, when I do this, testtools cmake run fails in its own test case adding:
-- Performing tests specific to dune-testtools from file /home/dune-ci/super/dune-testtools/cmake/modules/DuneTesttoolsMacros.cmake.
-- Installing python package at /home/dune-ci/super/dune-testtools/python into the virtualenv...
CMake Error at cmake/modules/DuneSystemtests.cmake:318 (_add_test):
_add_test given test NAME "dyntest1_1_0000" which already exists in this
directory.
Call Stack (most recent call first):
dune/testtools/test/dynamicvariants/CMakeLists.txt:5 (add_system_test_per_target)
This happens on 2.6 release branches with only dune-common + testtools. I'm attaching a dockerfile that recreates the failure in step 2 and in step 3 reverts the interpreter setting in config.opts and runs dunecontrol again without failure. I'm also attaching the full output of such a build.
I'm clueless as to what happens. Other than disabling all testing in all downstream modules and removing testtools from the module tree I see no workaround atm, and I'd rather not do that.