[D-runtime] auto-tester failing, local test passing

[Steve Schveighoffer]

>________________________________
>From: Brad Roberts <braddr at puremagic.com>
>To: d-runtime at puremagic.com
>Sent: Tuesday, June 21, 2011 11:29 AM
>Subject: Re: [D-runtime] auto-tester failing, local test passing
>
>On 6/21/2011 5:55 AM, Steve Schveighoffer wrote:
>> In the latest commit I just pulled (druntime pull request 29), the auto tester is now failing one of the unit tests.
>> 
>> However, on my local box (Linux 32-bit), the test passes...
>> 
>> I'm testing with dmd 2.053, and I think the auto-tester tests with the dmd out of github.  So that's the only thing I
>> can think of.  I was told that phobos/druntime developers should not be using the HEAD dmd, they should be using the
>> last released one.  Is this still true?
>> 
>> Sorry about the break, I hope I can figure out why soon.
>> 
>> -Steve
>
>The auto-tester always tests with the most recent submit of all three parts.  That's how releases are done so that's
>what needs to be tested.  For the most part, attempts are made to minimize the cross-package damage as changes are made,
>which helps minimize the number of times that upper layer developers HAVE to test with tip of everything, but that's not
>always the case.

OK, it looks like in this case it might have nothing to do with using HEAD, since I noticed after sending this message that the 32-bit tests are passing.  It looks more like a 64-bit problem, and I'm not sure if it's something I'm doing or not, I don't have a 64-bit box to test with.  I would suspect it might have something to do with the way I'm checking to see if the TypeInfo has overridden postblit.


I'll continue to test with the latest released dmd, unless it starts failing unit tests against the HEAD phobos/druntime.  I think that's probably the more reliable option.


>Regarding the 32/64 bit issues, you can over the cursor over each of the builds to get more details about it.  To short
>circuit that, the first number is how dmd is built (as a 32 or 64 bit application) and the second number is the output
>of dmd (32 bit or 64 bit code generation).

Thanks, I found this out seconds after sending this message :)  BTW the tester looks very spiffy!  I like the rounded edges, and the little color coded history on the right of the boxes.

>The windows test for both druntime and phobos is different than the posix platforms.  It does a big binary build rather
>than one binary per .d file.  I wish it was more like the posix test pattern, but no one has invested the time to change
>the win32 makefiles.

My concern is mostly this message in the passing output:

Warning 2: File Not Found druntime.lib

-Steve