Parallel execution of unittests

[Brad Anderson via Digitalmars-d]

On Thursday, 1 May 2014 at 17:24:58 UTC, Andrei Alexandrescu 
wrote:
> On 5/1/14, 10:09 AM, Steven Schveighoffer wrote:
>> On Thu, 01 May 2014 12:07:19 -0400, Dicebot 
>> <public at dicebot.lv> wrote:
>>
>>> On Thursday, 1 May 2014 at 15:37:21 UTC, Andrei Alexandrescu 
>>> wrote:
>>>> On 5/1/14, 8:04 AM, Dicebot wrote:
>>>>> On Thursday, 1 May 2014 at 14:55:50 UTC, Andrei 
>>>>> Alexandrescu wrote:
>>>>>> On 5/1/14, 1:34 AM, Dicebot wrote:
>>>>>>> I have just recently went through some of out internal 
>>>>>>> projects
>>>>>>> removing
>>>>>>> all accidental I/O tests for the very reason that /tmp 
>>>>>>> was full
>>>>>>
>>>>>> Well a bunch of stuff will not work on a full /tmp. Sorry, 
>>>>>> hard to
>>>>>> elicit empathy with a full /tmp :o). -- Andrei
>>>>>
>>>>> So you are OK with your unit tests failing randomly with no 
>>>>> clear
>>>>> diagnostics?
>>>>
>>>> I'm OK with my unit tests failing on a machine with a full 
>>>> /tmp. The
>>>> machine needs fixing. -- Andrei
>>>
>>> It got full because of tests (surprise!). Your actions?
>>
>> It would be nice to have a uniform mechanism to get a unique
>> system-dependent file location for each specific unit test.
>>
>> The file should automatically delete itself at the end of the 
>> test.
>
> Looks like /tmp (%TEMP% or C:\TEMP in Windows) in conjunction 
> with the likes of mkstemp is what you're looking for :o).
>
> Andrei

It hasn't been C:\TEMP for almost 13 years (before Windows XP 
which is now also end-of-life). Use GetTempPath.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa364992(v=vs.85).aspx