test: run unittests on test_dmd target for ci.sh

[ljmf00]

Signed-off-by: Luís Ferreira contact@lsferreira.net

[dlang-bot]

Thanks for your pull request, @ljmf00!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#13626"

[MoonlightSentinel]

Note that the unit tests are already run e.g. on Azure, see

dmd/.azure-pipelines/windows.sh

Lines 132 to 139 in cbd0b47

	targets=("all")
	args=('ARGS=-O -inline -g') # no -release for faster builds
	if [ "$HOST_DMD_VERSION" = "2.079.0" ] ; then
	# skip runnable_cxx and unit_tests with older bootstrap compilers
	targets=("runnable" "compilable" "fail_compilation" "dshell")
	args=() # use default set of args
	fi
	CC="$CC" ./run --environment --jobs=$N "${targets[@]}" "${args[@]}"

.

They are also explicitly disabled for bootstrap tests because some tests require a more recent host compiler.

EDIT: Given the state of the auto-tester it's probably better to leave the makefile unchanged and rather use run.d directly from ci.sh

[ljmf00]

Note that the unit tests are already run e.g. on Azure, see

Does that target generate coverage? auto-tester-test target is used on Cirrus CI tests too.

[ljmf00]

This seems to not merge the coverage reports. @RazvanN7 can you explain to me how the test runner merges coverage? I don't see any presence of --DRT-covopt="merge:1" and I'm not aware of the testing infrastructure good enough. Also, ./test/run.d -u and ./test/run.d unit_tests runs unit_test_runner on a different folders producing coverage on different places. The coverage is not being reported particularly, because ./test/run.d unit_tests runs inside ./test/ folder as its current working directory and before uploading codecov.sh does the following:

rm -rf test/runnable/extra-files test/*.lst

[MoonlightSentinel]

Does that target generate coverage? auto-tester-test target is used on Cirrus CI tests too.

Yes, allthough there's currently an issue that will be resolved in #13535 - just need to do some more debugging

[ljmf00]

Superseded by #13628 .