Re: Autotesting dub packages with dmd nightly
On Saturday, 16 July 2016 at 20:34:49 UTC, Sebastiaan Koppe wrote: Just to let you guys know - and to be sure no one is doing the same - I decided to go ahead and *start* writing an autotester that will fetch dmd nightly and unittest each dub package. It will be using a classic master-worker architecture and will leverage docker containers. I am aiming really low at first, but will eventually add things like memory usage, history, notifications, etc. Perhaps this code could also be used to find dub packages which are not currently compiling and mark them on code.dlang.org? Which is a feature which people have been asking for for a while.
Re: Autotesting dub packages with dmd nightly
On Saturday, 16 July 2016 at 20:34:49 UTC, Sebastiaan Koppe wrote: Just to let you guys know - and to be sure no one is doing the same - I decided to go ahead and *start* writing an autotester that will fetch dmd nightly and unittest each dub package. It will be using a classic master-worker architecture and will leverage docker containers. I am aiming really low at first, but will eventually add things like memory usage, history, notifications, etc. I think that everybody will agree that's an excellent ideas to discover regressions. How do you plan to handle libraries that are not purely written in D (i.e requiring -L-lClib linker option) ? There are probably other cases where a build failure won't be significant.
Re: DIP1001: Exception Handling Extensions
On 17/07/2016 5:35 AM, Superstar64 wrote: On Saturday, 16 July 2016 at 12:42:49 UTC, Andrei Alexandrescu wrote: Work much appreciated. Looks like the new community process works! -- Andrei I'm not sure you understand, I rejected my own PR. Exactly! It works :)
Re: Autotesting dub packages with dmd nightly
On 17/07/2016 8:34 AM, Sebastiaan Koppe wrote: Just to let you guys know - and to be sure no one is doing the same - I decided to go ahead and *start* writing an autotester that will fetch dmd nightly and unittest each dub package. It will be using a classic master-worker architecture and will leverage docker containers. I am aiming really low at first, but will eventually add things like memory usage, history, notifications, etc. If you add nightly can you add x last major releases? Also how about adding a 'button' for each one that says weather it passed or not and for which version of dmd.
Autotesting dub packages with dmd nightly
Just to let you guys know - and to be sure no one is doing the same - I decided to go ahead and *start* writing an autotester that will fetch dmd nightly and unittest each dub package. It will be using a classic master-worker architecture and will leverage docker containers. I am aiming really low at first, but will eventually add things like memory usage, history, notifications, etc.
Re: DIP1001: Exception Handling Extensions
On Saturday, 16 July 2016 at 12:42:49 UTC, Andrei Alexandrescu wrote: Work much appreciated. Looks like the new community process works! -- Andrei I'm not sure you understand, I rejected my own PR.
Re: DIP1001: Exception Handling Extensions
On 07/16/2016 12:51 AM, Superstar64 wrote: On Sunday, 10 July 2016 at 19:55:37 UTC, Superstar64 wrote: link: https://github.com/dlang/DIPs/pull/9 file: https://github.com/Superstar64/DIPs/blob/exception_extensions/DIPs/DIP1001.md I decided to close the PR. The my proposal had too many problems with it. Work much appreciated. Looks like the new community process works! -- Andrei
