[dmd-internals] dmd commit, revision 657

[Steve Schveighoffer]

When I run phobos unit tests, I get a few printouts like:

--- std.numeric(547) CustomFloat broken test ---

It seems to me like a good way to not forget about the test, but to also note 
that it's broken due to some compiler bug, is this a viable option for you?

-Steve



----- Original Message ----
> From: Jason House <jason.james.house at gmail.com>
> To: Discuss the internals of DMD <dmd-internals at puremagic.com>
> Sent: Thu, September 2, 2010 8:16:13 AM
> Subject: Re: [dmd-internals] dmd commit, revision 657
> 
> The practice of commenting out unit tests is generally a bad idea. 
>Historically,  I've seen it done a lot in Phobos. It's bad because such tests 
>are easily  forgotten about.
> 
> NUnit has the [Ignore] attribute. Other test suites have  expected failures. 
>The basic idea is to leave tests that fail due to a  legitimate bug such that 
>the overall result is success but the details still  show the problems.
> 
> As an example, cruise control with NUnit would  colorize status bars based on 
>what fraction of tests were success, failure, or  ignored. (green, red, and 
>yellow respectively) 
>
> 
> I'll get off my soap box  now...
> 
> Sent from my iPhone
> 
> On Sep 2, 2010, at 1:59 AM, "dsource.org" <noreply at dsource.org> wrote:
> 
> >  dmd commit, revision 657
> > 
> > 
> > user: braddr
> > 
> >  msg:
> > reenable fail274.d since the halt it was hitting has been  removed
> > 
> >  http://www.dsource.org/projects/dmd/changeset/657
> > 
> >  _______________________________________________
> > dmd-internals mailing  list
> > dmd-internals at puremagic.com
> > http://lists.puremagic.com/mailman/listinfo/dmd-internals
> _______________________________________________
> dmd-internals s mailing list
> dmd-internals at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-internals
>