In case not everyone knows about this, Brad Roberts conceived, implemented, set up and maintains an automated tester that watches github for checkins, and when there's something new it does a complete build of dmd and phobos, then runs the test suite on it, and posts the results:

http://d.puremagic.com/test-results/

I think it's awesome.

I too think it's awesome.

Just some quick thoughts;
 * Could some kind of benchmarking be integrated to track performance
aspects, especially find regressions? Perhaps a bit high on the
utility/work-scale?
 * Is the script available for running offline, on some local machine,
I.E. verifying different distro:s, etc?
 * 1280x1024 is too small for seeing the results. Could the view
perhaps be made slightly more compact? (Especially since OSX64 and
Win64 might be interesting targets in the near future?)
 * What is "Linux 32/64" vs. "64/32"?

In any case, great stuff.

2011/5/5 Walter Bright <newshound2@digitalmars.com>:
> In case not everyone knows about this, Brad Roberts conceived, implemented, set up and maintains an automated tester that watches github for checkins, and when there's something new it does a complete build of dmd and phobos, then runs the test suite on it, and posts the results:
>
> http://d.puremagic.com/test-results/
>
> I think it's awesome.
>

Am 05.05.2011 22:15, schrieb Ulrik Mikaelsson:
> I too think it's awesome.
> 
> Just some quick thoughts;
>  * Could some kind of benchmarking be integrated to track performance
> aspects, especially find regressions? Perhaps a bit high on the
> utility/work-scale?
>  * Is the script available for running offline, on some local machine,
> I.E. verifying different distro:s, etc?
>  * 1280x1024 is too small for seeing the results. Could the view
> perhaps be made slightly more compact? (Especially since OSX64 and
> Win64 might be interesting targets in the near future?)
>  * What is "Linux 32/64" vs. "64/32"?
> 

I *guess* Linux 32/64 means "32bit dmd generating 64bit binaries" and
"Linux 64/32" means "64bit dmd generating 32bit binaries".
Also note "Linux 64/64" ("64bit dmd generating 64bit binaries).

Seems like we get a native 64bit compiler for Linux. Awesome!

(But note that this is just my interpretation, maybe I'm wrong).

> In any case, great stuff.

I agree :)

> 
> 2011/5/5 Walter Bright <newshound2@digitalmars.com>:
>> In case not everyone knows about this, Brad Roberts conceived, implemented, set up and maintains an automated tester that watches github for checkins, and when there's something new it does a complete build of dmd and phobos, then runs the test suite on it, and posts the results:
>>
>> http://d.puremagic.com/test-results/
>>
>> I think it's awesome.
>>

On 05/05/2011 21:15, Ulrik Mikaelsson wrote:
> I too think it's awesome.
>
> Just some quick thoughts;
>   * Could some kind of benchmarking be integrated to track performance
> aspects, especially find regressions? Perhaps a bit high on the
> utility/work-scale?

Yes, this wouldn't be of much use though, as little work is done on the backend, and it only tracks dmd right now. It could perhaps be forked in a performance branch if someone were interested in that.

>   * Is the script available for running offline, on some local machine,
> I.E. verifying different distro:s, etc?

Yes, it's on github I believe, see the test/ directory of dmd. The server/client stuff is also available elsewhere I believe.

>   * 1280x1024 is too small for seeing the results. Could the view
> perhaps be made slightly more compact? (Especially since OSX64 and
> Win64 might be interesting targets in the near future?)

There was a recent discussion about this, there are plans to create a much cleaner and more compact view.

>   * What is "Linux 32/64" vs. "64/32"?

32 bit dmd creating 64 bit binaries, 64 bit dmd creating 32 bit binaries. I believe you get a description if you hover over them.

-- 
Robert
http://octarineparrot.com/

On Thu, 5 May 2011, Ulrik Mikaelsson wrote:

> Just some quick thoughts;
>  * Could some kind of benchmarking be integrated to track performance
> aspects, especially find regressions? Perhaps a bit high on the
> utility/work-scale?

Could? Yes.
Am I going to? Not likely.  If someone else does, it could be
incorporated.

>  * Is the script available for running offline, on some local machine,
> I.E. verifying different distro:s, etc?

There's a link to the scripts at the bottom of the page.  They're hosted on github.  I've often got parts that aren't yet checked in but nothing that's particularly central to the testing.

>  * 1280x1024 is too small for seeing the results. Could the view
> perhaps be made slightly more compact? (Especially since OSX64 and
> Win64 might be interesting targets in the near future?)

See answers from the others.  But in general, sorry.  I'm catering to the people who are doing the primary development, and most have nice large and wide screens.

>  * What is "Linux 32/64" vs. "64/32"?

As indicated already, hover over each of the titles for a longer description of the build.

Later,
Brad

Awesome stuff!

One small comments. Have you thought about displaying it as a table? A lot of words are duplicated hence wasting precious display space. The table can look as follows:

                                Linux x86          ...
                         compile    unittest     ...
         dmd
00:00 druntime
         phobos

...

Hopefully that displays correctly...

-Jose
On Thu, May 5, 2011 at 6:21 PM, Brad Roberts <braddr@puremagic.com> wrote:
> On Thu, 5 May 2011, Ulrik Mikaelsson wrote:
>
>> Just some quick thoughts;
>>  * Could some kind of benchmarking be integrated to track performance
>> aspects, especially find regressions? Perhaps a bit high on the
>> utility/work-scale?
>
> Could? Yes.
> Am I going to? Not likely.  If someone else does, it could be
> incorporated.
>
>>  * Is the script available for running offline, on some local machine, I.E. verifying different distro:s, etc?
>
> There's a link to the scripts at the bottom of the page.  They're hosted on github.  I've often got parts that aren't yet checked in but nothing that's particularly central to the testing.
>
>>  * 1280x1024 is too small for seeing the results. Could the view perhaps be made slightly more compact? (Especially since OSX64 and Win64 might be interesting targets in the near future?)
>
> See answers from the others.  But in general, sorry.  I'm catering to the people who are doing the primary development, and most have nice large and wide screens.
>
>>  * What is "Linux 32/64" vs. "64/32"?
>
> As indicated already, hover over each of the titles for a longer description of the build.
>
> Later,
> Brad
>
>

On 2011-05-05 23:21, Brad Roberts wrote:
> On Thu, 5 May 2011, Ulrik Mikaelsson wrote:
>
>> Just some quick thoughts;
>>   * Could some kind of benchmarking be integrated to track performance
>> aspects, especially find regressions? Perhaps a bit high on the
>> utility/work-scale?
>
> Could? Yes.
> Am I going to? Not likely.  If someone else does, it could be
> incorporated.
>
>>   * Is the script available for running offline, on some local machine,
>> I.E. verifying different distro:s, etc?
>
> There's a link to the scripts at the bottom of the page.  They're hosted
> on github.  I've often got parts that aren't yet checked in but nothing
> that's particularly central to the testing.
>
>>   * 1280x1024 is too small for seeing the results. Could the view
>> perhaps be made slightly more compact? (Especially since OSX64 and
>> Win64 might be interesting targets in the near future?)
>
> See answers from the others.  But in general, sorry.  I'm catering to the
> people who are doing the primary development, and most have nice large and
> wide screens.

I have a display with a 1680x1050 resolution, it fills up the whole screen, no more room for additional platforms without scrolling. Still too small?

>>   * What is "Linux 32/64" vs. "64/32"?
>
> As indicated already, hover over each of the titles for a longer
> description of the build.
>
> Later,
> Brad
>


-- 
/Jacob Carlborg

On 05/05/2011 20:19, Walter Bright wrote:
> In case not everyone knows about this, Brad Roberts conceived,
> implemented, set up and maintains an automated tester that watches
> github for checkins, and when there's something new it does a complete
> build of dmd and phobos, then runs the test suite on it, and posts the
> results:
>
> http://d.puremagic.com/test-results/
>
> I think it's awesome.

Awesome indeed. Continuous integration is a very beneficial technique for software development.

-- 
Bruno Medeiros - Software Engineer

"Jacob Carlborg" <doob@me.com> wrote in message news:iq0653$5fh$1@digitalmars.com...
> On 2011-05-05 23:21, Brad Roberts wrote:
>> On Thu, 5 May 2011, Ulrik Mikaelsson wrote:
>>
>>>   * 1280x1024 is too small for seeing the results. Could the view
>>> perhaps be made slightly more compact? (Especially since OSX64 and
>>> Win64 might be interesting targets in the near future?)
>>
>> See answers from the others.  But in general, sorry.  I'm catering to the
>> people who are doing the primary development, and most have nice large
>> and
>> wide screens.
>
> I have a display with a 1680x1050 resolution, it fills up the whole screen, no more room for additional platforms without scrolling. Still too small?
>

My monitor is a beefy 21", but I have it set to 1152x864 because any more than that and all the UI elements are too small. Definitely can't fit that page in one screen without horizontal scrolling. Although since it's just a series a small tables (arranged in a table) I don't really mind the horizontal scrolling all that much. (Although I certainly wouldn't object to a less horizontally-intensive design. Not that I'm really one of the primary target users for it, though.)

"Robert Clipsham" <robert@octarineparrot.com> wrote in message news:ipv3tv$1eg0$1@digitalmars.com...
>
>>   * What is "Linux 32/64" vs. "64/32"?
>
> 32 bit dmd creating 64 bit binaries, 64 bit dmd creating 32 bit binaries. I believe you get a description if you hover over them.
>

Probably a stupid question, but 32-bit DMD can't create 64-bit binaries when running on a 32-bit system, can it? I assume 32-bit DMD can only create 64-bit binaries when running on a 64-bit system, right?