• Dicebot (16/16) Dec 14 2014 Short story about my attempt to put a bit more efforts in
• Joseph Rushton Wakeling (9/25) Dec 16 2014 Thanks very much for this, it's a very valuable piece of work.
• Dicebot (4/12) Dec 16 2014 Done. Send me an e-mail to public@dicebot.lv with your e-mail to
• Joseph Rushton Wakeling (22/25) Dec 20 2014 Well, that nudged me to get some fixes done, at least :-)
• Dicebot (9/16) Dec 21 2014 I had that idea in mind for quite some time now, at some point we

"Dicebot" <public dicebot.lv> writes:

Short story about my attempt to put a bit more efforts in 
detecting user projects breakage by compiler changes:

http://blog.dicebot.lv/2014/12/making-sure-your-d-projects-wont-break.html

Quoting important bit:

"It is quite likely that only few of you will want to spend that 
much time to simply be able to report regressions in time. I'd 
still want to see much more healthy library ecosystem out there 
thus simple proposal - poke me via e-mail and I will gladly add 
any of you projects to the system I have already configured. 
There is a one requirement though : you must be willing to 
actually investigate found regressions and report them to 
bugzilla or workaround in your project. If that sounds OK to you, 
just let me know"

Ironically not a single of few projects I have tried adding 
currently compiles with a dmd git master - will add more as 
issues get resolved.

"Joseph Rushton Wakeling" <joseph.wakeling webdrake.net> writes:

On Monday, 15 December 2014 at 05:51:56 UTC, Dicebot wrote:
 Short story about my attempt to put a bit more efforts in 
 detecting user projects breakage by compiler changes:

 http://blog.dicebot.lv/2014/12/making-sure-your-d-projects-wont-break.html

 Quoting important bit:

 "It is quite likely that only few of you will want to spend 
 that much time to simply be able to report regressions in time. 
 I'd still want to see much more healthy library ecosystem out 
 there thus simple proposal - poke me via e-mail and I will 
 gladly add any of you projects to the system I have already 
 configured. There is a one requirement though : you must be 
 willing to actually investigate found regressions and report 
 them to bugzilla or workaround in your project. If that sounds 
 OK to you, just let me know"

 Ironically not a single of few projects I have tried adding 
 currently compiles with a dmd git master - will add more as 
 issues get resolved.

Thanks very much for this, it's a very valuable piece of work.

I'd be very happy if you were to add
https://github.com/WebDrake/Dgraph
https://github.com/WebDrake/hap

to your testing list.  I've just tried them out with latest 
git-master dmd and pushed appropriate fixes (Dgraph had some 
arrays declared C-style, hap.random had some typetuple import 
failures).

"Dicebot" <public dicebot.lv> writes:

On Wednesday, 17 December 2014 at 01:40:05 UTC, Joseph Rushton 
Wakeling wrote:
 Thanks very much for this, it's a very valuable piece of work.

 I'd be very happy if you were to add
 https://github.com/WebDrake/Dgraph
 https://github.com/WebDrake/hap

 to your testing list.  I've just tried them out with latest 
 git-master dmd and pushed appropriate fixes (Dgraph had some 
 arrays declared C-style, hap.random had some typetuple import 
 failures).

Done. Send me an e-mail to public dicebot.lv with your e-mail to 
put for build failure notifications

"Joseph Rushton Wakeling" <joseph.wakeling webdrake.net> writes:

On Monday, 15 December 2014 at 05:51:56 UTC, Dicebot wrote:
 Ironically not a single of few projects I have tried adding 
 currently compiles with a dmd git master - will add more as 
 issues get resolved.

Well, that nudged me to get some fixes done, at least :-)

I'd like to reiterate my thanks for what I think will be a really 
key bit of work in providing rigorous quality assurance for D.  
It's something that I've wanted to see for a long time:
http://forum.dlang.org/thread/mailman.47.1369319426.13711.digitalmars-d puremagic.com

... but didn't have the time or expertise to address, so I'm 
really grateful you have stepped up to deliver this.

I'd really encourage other people with dub-compliant projects to 
sign up; let's leverage these testing opportunities to ensure 
both that our projects don't suffer bitrot, and that we have a 
good advance warning of any unintended (or intended!) breaking 
changes in the compiler and/or libraries.

In the longer run, it'd be great if this could become an official 
part of the D testing framework accessible from dlang.org.  It 
would also be really nice if we could have some sort of link 
between this system, and the project list on code.dlang.org: 
perhaps a traffic-light system where a project is marked green if 
it's compatible with current D release, amber if it works but 
triggers warnings, and red if it fails?

Whatever the future allows, thanks once again for being awesome 
:-)

"Dicebot" <public dicebot.lv> writes:

On Sunday, 21 December 2014 at 00:14:18 UTC, Joseph Rushton 
Wakeling wrote:
 In the longer run, it'd be great if this could become an 
 official part of the D testing framework accessible from 
 dlang.org.  It would also be really nice if we could have some 
 sort of link between this system, and the project list on 
 code.dlang.org: perhaps a traffic-light system where a project 
 is marked green if it's compatible with current D release, 
 amber if it works but triggers warnings, and red if it fails?

I had that idea in mind for quite some time now, at some point we 
have been discussing with Sonke what would it take to add such 
integration. But it is non-trivial effort to get it right and 
actually useful and I have never had opportunity to spend that 
much time in a single chunk since then.

Thus I decided to go with a more simple non-automated approach 
for now.