# Windows buildserver test run

**URL:** <https://www.ruby-forum.com/t/windows-buildserver-test-run/177901>\
**Category:** IronRuby\
**Created:** [October 26, 2009, 2:13pm UTC](https://www.ruby-forum.com/t/windows-buildserver-test-run/177901 "2009-10-26T14:13:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![barby](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/c57346/32.png) [@barby](https://www.ruby-forum.com/u/barby)\
**Post date:** [October 26, 2009, 2:13pm UTC](https://www.ruby-forum.com/t/windows-buildserver-test-run/177901/1 "2009-10-26T14:13:39Z")

</div>

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))