www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Unittest assertion failure messages in OSX

reply "Kapps" <opantm2+spam gmail.com> writes:
With git master using OSX Mavericks I'm noticing that I'm no 
longer seeing any assertion failure messages from inside unittest 
blocks.

For example with:
import std.stdio;

unittest {
	writeln("Reached unittest.");
	assert(0);
	writeln("After failed assertion.");
}

Output:
rdmd -main -unittest test2.d
Reached unittest.


Replacing unittest with void main(), the assertion message prints 
out properly. Is this something that's just odd with my setup, or 
is this happening to others running OSX / git master?
Oct 26 2013
next sibling parent Jacob Carlborg <doob me.com> writes:
On 2013-10-26 09:12, Kapps wrote:

 With git master using OSX Mavericks I'm noticing that I'm no longer
 seeing any assertion failure messages from inside unittest blocks.

 For example with:
 import std.stdio;

 unittest {
      writeln("Reached unittest.");
      assert(0);
      writeln("After failed assertion.");
 }

 Output:
 rdmd -main -unittest test2.d
 Reached unittest.


 Replacing unittest with void main(), the assertion message prints out
 properly. Is this something that's just odd with my setup, or is this
 happening to others running OSX / git master?


I can confirm that on Mac OS X Mountain Lion as well.

-- 
/Jacob Carlborg
Oct 26 2013
prev sibling next sibling parent reply Jacob Carlborg <doob me.com> writes:
On 2013-10-26 09:12, Kapps wrote:

 With git master using OSX Mavericks I'm noticing that I'm no longer
 seeing any assertion failure messages from inside unittest blocks.

 For example with:
 import std.stdio;

 unittest {
      writeln("Reached unittest.");
      assert(0);
      writeln("After failed assertion.");
 }

 Output:
 rdmd -main -unittest test2.d
 Reached unittest.


 Replacing unittest with void main(), the assertion message prints out
 properly. Is this something that's just odd with my setup, or is this
 happening to others running OSX / git master?


Reported as: http://d.puremagic.com/issues/show_bug.cgi?id=11362.

-- 
/Jacob Carlborg
Oct 26 2013
parent =?UTF-8?B?QWxpIMOHZWhyZWxp?= <acehreli yahoo.com> writes:
On 10/26/2013 05:09 AM, Jacob Carlborg wrote:


 Reported as: http://d.puremagic.com/issues/show_bug.cgi?id=11362.


Same on Linux. :( I have already updated the bug.

Bad bug, bad!

Ali
Oct 26 2013
prev sibling parent reply =?UTF-8?B?QWxpIMOHZWhyZWxp?= <acehreli yahoo.com> writes:
On 10/26/2013 12:12 AM, Kapps wrote:

 With git master using OSX Mavericks I'm noticing that I'm no longer
 seeing any assertion failure messages from inside unittest blocks.

 For example with:
 import std.stdio;

 unittest {
      writeln("Reached unittest.");
      assert(0);
      writeln("After failed assertion.");
 }

 Output:
 rdmd -main -unittest test2.d
 Reached unittest.


 Replacing unittest with void main(), the assertion message prints out
 properly. Is this something that's just odd with my setup, or is this
 happening to others running OSX / git master?


Ping.

Could others chime in and reopen this bug please. It has just been 
closed as WORKSFORWALTER. ;)

   http://d.puremagic.com/issues/show_bug.cgi?id=11362

Ali
Oct 27 2013
parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 10/27/2013 11:59 PM, Ali Çehreli wrote:

 Could others chime in and reopen this bug please. It has just been closed as
 WORKSFORWALTER. ;)

    http://d.puremagic.com/issues/show_bug.cgi?id=11362


Correction: it worksforme in the 2.064 beta. The commit that broke it occurs 
only in the 2.065 master.
Oct 28 2013
parent =?UTF-8?B?QWxpIMOHZWhyZWxp?= <acehreli yahoo.com> writes:
On 10/28/2013 12:31 AM, Walter Bright wrote:

 On 10/27/2013 11:59 PM, Ali Çehreli wrote:

 Could others chime in and reopen this bug please. It has just been
 closed as
 WORKSFORWALTER. ;)

    http://d.puremagic.com/issues/show_bug.cgi?id=11362


 Correction: it worksforme in the 2.064 beta. The commit that broke it
 occurs only in the 2.065 master.


Thank you! :)

Ali
Oct 28 2013