Re: Compile all-of-dub?

2015-09-11 Thread Martin Nowak via Digitalmars-d
On 09/11/2015 01:37 PM, ZombineDev wrote: > On Wednesday, 9 September 2015 at 08:26:59 UTC, qznc wrote: >> ... > > https://github.com/MartinNowak/project_tester Right, please contribute.

Re: Compile all-of-dub?

2015-09-11 Thread Martin Nowak via Digitalmars-d
On 09/09/2015 10:26 AM, qznc wrote: > The Rust people have this Crater [0,1] tool, which essentially builds > all Rust libraries with two compiler versions and compares for regressions. I recently created a Jenkins project so that I can easily test many projects with a particular DPL version or

Re: Compile all-of-dub?

2015-09-11 Thread ZombineDev via Digitalmars-d
On Wednesday, 9 September 2015 at 08:26:59 UTC, qznc wrote: ... https://github.com/MartinNowak/project_tester

Re: Compile all-of-dub?

2015-09-09 Thread Rikki Cattermole via Digitalmars-d
On 09/09/15 8:26 PM, qznc wrote: The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for regressions. Since D has a central library repository as well, it would make sense to do this broad testing as well. We don't

Compile all-of-dub?

2015-09-09 Thread qznc via Digitalmars-d
The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for regressions. Since D has a central library repository as well, it would make sense to do this broad testing as well. We don't have nightly builds (or do we?),

Re: Compile all-of-dub?

2015-09-09 Thread Sebastiaan Koppe via Digitalmars-d
On Wednesday, 9 September 2015 at 08:26:59 UTC, qznc wrote: The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for regressions. Since D has a central library repository as well, it would make sense to do this broad

Re: Compile all-of-dub?

2015-09-09 Thread Jacob Carlborg via Digitalmars-d
On 2015-09-09 10:26, qznc wrote: The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for regressions. Since D has a central library repository as well, it would make sense to do this broad testing as well. We don't

Re: Compile all-of-dub?

2015-09-09 Thread Edwin van Leeuwen via Digitalmars-d
On Wednesday, 9 September 2015 at 08:56:56 UTC, Rikki Cattermole wrote: On 09/09/15 8:26 PM, qznc wrote: The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for regressions. Since D has a central library repository

Re: Compile all-of-dub?

2015-09-09 Thread Rikki Cattermole via Digitalmars-d
On 09/09/15 9:21 PM, Edwin van Leeuwen wrote: On Wednesday, 9 September 2015 at 08:56:56 UTC, Rikki Cattermole wrote: On 09/09/15 8:26 PM, qznc wrote: The Rust people have this Crater [0,1] tool, which essentially builds all Rust libraries with two compiler versions and compares for

Re: Compile all-of-dub?

2015-09-09 Thread Jack Stouffer via Digitalmars-d
On Wednesday, 9 September 2015 at 12:02:55 UTC, Jacob Carlborg wrote: I think it's a great idea. This has been suggested before. The objections were that: * If you do find a problem who should be responsible for figuring out if it's a regression or an intended change? * Not all packages are

Re: Compile all-of-dub?

2015-09-09 Thread qznc via Digitalmars-d
On Wednesday, 9 September 2015 at 08:56:56 UTC, Rikki Cattermole wrote: Or use travis-ci. They have that as well: http://rust-ci.org/

Re: Compile all-of-dub?

2015-09-09 Thread qznc via Digitalmars-d
On Wednesday, 9 September 2015 at 12:02:55 UTC, Jacob Carlborg wrote: I think it's a great idea. This has been suggested before. The objections were that: * If you do find a problem who should be responsible for figuring out if it's a regression or an intended change? It does raise the bar

Re: Compile all-of-dub?

2015-09-09 Thread ponce via Digitalmars-d
On Wednesday, 9 September 2015 at 13:48:16 UTC, qznc wrote: On Wednesday, 9 September 2015 at 12:02:55 UTC, Jacob Carlborg wrote: I think it's a great idea. This has been suggested before. The objections were that: * If you do find a problem who should be responsible for figuring out if it's