closer changed the topic of #ruby-core to: check the latest release candidate for 1.9.1 release ftp.ruby-lang.org:/home/yugui/ruby-1.9.1-r26021+1.tar.bz2
<znz_jp>
biff: [ruby-changes:37669] usa:r49750 (trunk): * ext/win32/Win32API.rb (initialize): accept both a string and an array - http://mla.n-z.jp/?ruby-changes=37669
<hsbt>
I got these fails when running make test-rubyspec on ruby repository
<hsbt>
fmmm
<eregon>
did you change the branch you use?
<hsbt>
I rebuild trunk and running again
<eregon>
hsbt: did you change to master in spec/mspec and spec/rubyspec?
<hsbt>
Yes, I did
<hsbt>
Probably, my ruby binary is old
<hsbt>
I got 1F 0E, 1F is my environment issue.
<hsbt>
It's ok!
<eregon>
:)
<eregon>
hsbt: I have an issue due to the spec/default.rb pointing ro ruby.mspec
<hsbt>
I changed default branch again tommoro, ( Now, 22:30 JST )
<eregon>
ah you fixed it already
<eregon>
ok!
<hsbt>
Thanks your incredible effort!
<eregon>
thanks, you are welcome!
<eregon>
I noticed some SEGV from time to time on 2.0.0 in CAPI specs, let's see if RubyCI catch them, they probably are bugs either in 2.0.0 or in the spec C code
djellemah has joined #ruby-core
<djellemah>
Hi everyone. From ext/thread/thread.c, what's a better way to do this: strcmp("aborting", RSTRING_PTR(rb_funcall(thread,rb_intern("status"),0))) == 0 Thanks