[Ironruby-core] windows buildserver test run

Jim Deville jdeville at microsoft.com
Mon Oct 26 11:09:53 EDT 2009

Default.mspec has a trace handler that causes assserts to print a message instead of the dialog if %SILENTASSERT% is set. This listener could be ported to a different location to make it work across the test runners.


From: Ivan Porto Carrero <ivan at flanders.co.nz>
Sent: Monday, October 26, 2009 6:13 AM
To: ironruby-core <ironruby-core at rubyforge.org>
Subject: [Ironruby-core] windows buildserver test run


I just kicked off a new build on the buildserver but I think we should come up with a better way of using tracing the debug assert statements in a ci build. Currently they are displayed using a message box. Last time there were only a couple of these  popping up this time around when it runs the suite after RubySpec B it has hundreds of them.
I disabled the diagnostics listeners for now so the build can proceed without me having to hammer spacebar for about 20 minutes.

github seems to have a probleem with invoking the builds remotely so I'll set up polling on a daily schedule.

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091026/e3ab4320/attachment.html>

More information about the Ironruby-core mailing list