The problem stems from this change <
https://github.com/boostorg/qvm/commit/b22b5868205653efc96b4c42c31c0294b0bc4...
. The test & report system uses the test paths to determine various things including the library the test belongs to and the *sub-library* it belongs to. When you moved the test targets (what's in the Jamfile) the path changed. And from that point onwards the test paths, instead of looking like the library tests, started looking like sub-library tests. Specifically the test info references used to look like:
boost-test(COMPILE) "qvm/hdrqvm-all~hpp" : "libs/qvm/test/header-test.cpp"
And now they look like:
boost-test(COMPILE) "qvm/bld/hdrqvm-all~hpp" : "libs/qvm/test/header-test.cpp"
I did looked at the test and reporting code and did some experiments... And I don't see any good way to adjust to how you structured your tests without adversely impacting the support for sub-libraries. Best I can suggest for now is to move the test targets back into the qvm/test/Jamfile.v2 file.
Yes I wanted to move the targets out from qvm/test, I guess that won't work. I'll move them back into qvm/test. Thanks! Emil