D-thrift package detects regressions since 2.061, where is the regression suite located?

David d at dav1d.de
Fri Aug 23 15:11:33 PDT 2013


Am 23.08.2013 20:07, schrieb Walter Bright:
> On 8/23/2013 10:34 AM, Denis Shelomovskij wrote:
>> By the way, the ability to add costume projects to D autotester is
>> already
>> proposed without any response:
>> http://forum.dlang.org/thread/kqm4ta$m7f$1@digitalmars.com
>>
> 
> The question comes up repeatedly, and I've answered it repeatedly, the
> latest on 8/20 in the thread "std.serialization: pre-voting review /
> discussion". Here's the message:
> ---------------------------------
> On 8/18/2013 9:33 AM, David Nadlinger wrote:
>> Having a system that regularly, automatically runs the test suites of
> several
>> larger, well-known D projects with the results being readily available
> to the
>> DMD/druntime/Phobos teams would certainly help. But it's also not
> ideal, since
>> if a project starts to fail, the exact nature of the issue (regression
> in DMD or
>> bug in the project, and if the former, a minimal test case) can often
> be hard to
>> track down for somebody not already familiar with the code base.
> 
> That's exactly the problem. If these large projects are incorporated
> into the autotester, who is going to isolate/fix problems arising with
> them?
> 
> The test suite is designed to be a collection of already-isolated
> issues, so understanding what went wrong shouldn't be too difficult.
> Note that already it is noticeably much harder to debug a phobos unit
> test gone awry than the other tests. A full blown project that nobody
> understands would fare far worse.
> 
> (And the other problem, of course, is the test suite is designed to be
> runnable fairly quickly. Compiling some other large project and running
> its test suite can make the autotester much less useful when the
> turnaround time increases.)
> 
> Putting large projects into the autotester has the implication that
> development and support of those projects has been ceded to the core dev
> team, i.e. who is responsible for it has been badly blurred.
> 

I find it funny how hard you try to get D "production ready" and make
(in my opinion) bad decisions affecting the future of D, but I hit every
release at least 3 regressions, 1 of these is mostly a real WTF.

At least run this test-suite consisting of 3rd party projects every now
and then and especially before a release. I personally don't mind these
regressions (well I do, but I can live with them), trying to find the
root for a day or two and fix it there, but companies will. While we're
at it, the D release-zip should also be checked, not beeing able to
install a new release because the zip is fucked up doesn't speak for D
(especially when it takes forever to download dmd for windows and you
find a shitton of binaries for other OSes as well)
</rant>


More information about the Digitalmars-d mailing list