• wolframw (9/9) Sep 22 2018 Hi,
• Jacob Carlborg (6/18) Sep 25 2018 I'm guessing because originally there weren't that many unit test blocks...

wolframw <wolframw protonmail.com> writes:

Hi,

I ran the dmd unittests on my Windows machine today and one of 
the tests in filename.d asserted. The cause for this has already 
been noticed a few days ago by someone else [1] but not by CI.

Is it well-known that the dmd unittests (at least for the Windows 
build) are not automatically run? If so, what is the reasoning 
behind it?


[1] 
https://github.com/dlang/dmd/commit/7baa0e82802839940fb0620bad02e97f741d2c27#r30571264

Jacob Carlborg <doob me.com> writes:

On 2018-09-22 15:29, wolframw wrote:
 Hi,
 
 I ran the dmd unittests on my Windows machine today and one of the tests 
 in filename.d asserted. The cause for this has already been noticed a 
 few days ago by someone else [1] but not by CI.
 
 Is it well-known that the dmd unittests (at least for the Windows build) 
 are not automatically run? If so, what is the reasoning behind it?
 
 
 [1] 
 https://github.com/dlang/dmd/commit/7baa0e82802839940fb0620bad02e9
f741d2c27#r30571264 

I'm guessing because originally there weren't that many unit test blocks 
in the DMD source (or any at all). The main test suite is in the 
separate directory "tests".

-- 
/Jacob Carlborg