DTrace tst.gcc.d isn't useful
the DTrace tests contain a test, tst.gcc.d, which is the same as tst.coverage.d, except built using GCC.
This made sense when Studio was the primary compiler, and likely to remain so, but currently leaves it duplicate.
Further, in a multi-shadow world (#9128) there's no realistic way to say "Build this test with every other compiler". We should just remove it.
Updated by Electric Monk over 2 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit aa9ef484c6f8ecee85dfefdb4970c50cfa2db302 Author: John Levon <email@example.com> Date: 2018-10-04T00:34:40.000Z 9128 cw(1onbld) should be able to run multiple shadows 9129 file-locking tests shouldn't build multiple source files in one compiler invocation 9130 DTrace tst.gcc.d isn't useful 9132 cw(1onbld) shouldn't shadow pure preprocessing Portions contributed by: Richard Lowe <firstname.lastname@example.org> Reviewed by: Andy Fiddaman <email@example.com> Approved by: Dan McDonald <firstname.lastname@example.org>