# SVN Revsion 70

**URL:** <https://www.ruby-forum.com/t/svn-revsion-70/125398>\
**Category:** IronRuby\
**Created:** [January 8, 2008, 9:00pm UTC](https://www.ruby-forum.com/t/svn-revsion-70/125398 "2008-01-08T21:00:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_LSSDLR](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@John\_LSSDLR](https://www.ruby-forum.com/u/John_LSSDLR)\
**Post date:** [January 8, 2008, 9:00pm UTC](https://www.ruby-forum.com/t/svn-revsion-70/125398/1 "2008-01-08T21:00:38Z")

</div>

I just pushed out our latest SVN release. Included is the Socket  
contribution from Terence L. (thanks!).

Other highlights of this release (for folks building libraries) are:

An implementation of IO that implements console and file operations.  
STDOUT, STDIN, STDERR are all implemented now.

An updated test running infrastructure that supports running specs  
individually. Here are some examples:

1. Run all IO specs:

rake spec io

1. Run a specific IO spec (seek):

rake spec io seek

1. Run a specific IO spec with a different reporter, fail, which dumps  
stack traces only for the failed specs.

rake spec io seek fail

1. Run all IO specs with the fail reporter:

rake spec io - fail

The specs also support exclusions as well - see the .spec/\* files for  
each type for examples. It’s probably a good idea to drive all specs to  
zero failures using exclusions. The next piece of work we’re going to do  
is exactly this so that we can use the specs to detect regressions in  
our SNAP testing harness (this is the farm of machines that we use to  
run IronRuby on all supported configurations / platforms).

Thanks,  
-John

---

<div class="post-metadata">

**Author:** ![John\_LSSDLR](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@John\_LSSDLR](https://www.ruby-forum.com/u/John_LSSDLR)\
**Post date:** [January 9, 2008, 10:20pm UTC](https://www.ruby-forum.com/t/svn-revsion-70/125398/2 "2008-01-09T22:20:39Z")

</div>

John L. wrote:

> > An updated test running infrastructure that supports running specs  
> > individually.

and

> > The next piece of work we’re going to do is exactly this so that we can  
> > use the specs to detect regressions in our SNAP testing harness (this is  
> > the  
> > farm of machines that we use to run IronRuby on all supported  
> > configurations  
> > / platforms).

I notice from the rake file that the :test\_libs task is going to become  
obsolete soon. From the look of this email, it seems that all tests  
written  
in Ruby are now basically Rubinius specs. Is this the case? What  
happens  
if we right our own specs for IronRuby? Do we have to get them included  
in  
the Rubinius specs in order that they filter down to the IronRuby  
codebase?

Cheers,  
Pete

---

<div class="post-metadata">

**Author:** ![John\_LSSDLR](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/5f8ce5/32.png) [@John\_LSSDLR](https://www.ruby-forum.com/u/John_LSSDLR)\
**Post date:** [January 9, 2008, 10:24pm UTC](https://www.ruby-forum.com/t/svn-revsion-70/125398/3 "2008-01-09T22:24:12Z")

</div>

Peter Bacon D.:

> I notice from the rake file that the :test\_libs task is going to become  
> obsolete soon. From the look of this email, it seems that all tests  
> written  
> in Ruby are now basically Rubinius specs. Is this the case? What  
> happens  
> if we right our own specs for IronRuby? Do we have to get them  
> included in  
> the Rubinius specs in order that they filter down to the IronRuby  
> codebase?

The library tests will be rubinius specs. However, we will continue to  
use lower-level test harnesses for testing the language.

I’m working with Brian F. to figure out what to do about integrating  
changes back into the rubinius specs (which will have their own home  
sometime soon). I’ve already checked in additional specs for IO into our  
tree.

I think it should be fine to continue to work on our additions in  
parallel and then RI those changes back into the ruby spec tree once it  
gets spun up.

Thanks,  
-John