# Re: windows buildserver test run **URL:** \ **Category:** IronRuby\ **Created:** [October 26, 2009, 4:25pm UTC](https://www.ruby-forum.com/t/re-windows-buildserver-test-run/177908 "2009-10-26T16:25:23Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![raker\_t](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/ecae2f/32.png) [@raker\_t](https://www.ruby-forum.com/u/raker_t)\ **Post date:** [October 26, 2009, 4:25pm UTC](https://www.ruby-forum.com/t/re-windows-buildserver-test-run/177908/1 "2009-10-26T16:25:23Z")
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. JD * * * From: Ivan Porto C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Sent: Monday, October 26, 2009 6:13 AM To: ironruby-core [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) Subject: [Ironruby-core] windows buildserver test run Hi, 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 C. Blog: [http://flanders.co.nz](http://flanders.co.nz) Twitter: [http://twitter.com/casualjim](http://twitter.com/casualjim) Author of IronRuby in Action ([http://manning.com/carrero](http://manning.com/carrero))