From: Benoit Daloze Date: 2015-02-23T11:53:40+01:00 Subject: [ruby-core:68249] Re: What to do with rubyspec errors (was: Re: Re: Future of test suites for Ruby) --047d7b3a9a847b5f90050fbf39f0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Martin, It seems a known issue, but I think it is possible to fix. Could you run with the specdoc formatter, like $ mspec -fs That should show the examples which are blocking. You should report the bug on https://github.com/ruby/mspec or https://github.com/ruby/rubyspec. Regards, Benoit On 23 February 2015 at 11:16, "Martin J. D=C3=BCrst" wrote: > Hello Anthony, > > Maybe you can help me. I'm frequently compiling CRuby trunk on cygwin, an= d > occasionally tried to run rubyspec (make test-rubyspec). However, I alway= s > get the same result: Some lines of textual output, then about 7 lines of > mostly dots with a few Fs and an occasional E or two, and then the thing > hangs with a busy ruby executable, which I have to kill via the task > manager (Ctrl-C doesn't help). > > I'd like to be able to submit bug reports, either for the spec or for the > implementation, but I don't know what's wrong where I get Fs, and I don't > know which test produced an endless loop. I didn't get any help from > http://rubyspec.org/mspec/, but maybe that's the wrong place to look. > > Regards, Martin. > > On 2015/02/17 22:16, Anthony Crumley wrote: > >> Beniot, >> >> I have been working on reconciling RubySpec with the 2.x MRI versions ov= er >> the last month. https://github.com/anthonycrumley/rubyspec/ >> commits/master >> >> My intention is to: >> 1) Get RubySpec updated to run with all the 2.x versions of MRI. >> 2) Get the nurse/rubyspec updates since the fork added. >> 3) Get the updated RubySpecs into the MRI CI. >> 4) Hopefully find that repo a home at either rubyspec/rubyspec or >> ruby/rubyspec. >> >> I agree with you that the RubySpec tests are very valuable and would LOV= E >> to work with you on them. >> >> Anthony >> >> On Tue Feb 17 2015 at 6:59:48 AM Benoit Daloze >> wrote: >> >> On 17 February 2015 at 13:32, Benoit Daloze wrote: >>> >>> - The second step is really to choose a canonical RubySpec repository, >>>> to >>>> avoid "death by too much forks". >>>> This repository should only contain RubySpec tests for practical >>>> reasons. >>>> We should allow many specs contributors to take part in merging change= s >>>> and maintaining specs. >>>> I think this was a fatal flaw of rubyspec/rubyspec in that too few >>>> people >>>> had the large burden of merging and maintaining the specs. >>>> >>>> The main existing repository I see today is nurse/rubyspec. >>>> I am thinking the process could be similar to handling pull requests o= n >>>> ruby/ruby in that some contributors would provide feedback and merge >>>> them. >>>> The CI is very useful in this regard to ensure MRI is not broken >>>> inadvertently. >>>> >>>> >>> I think it would make sense in that case to move nurse/rubyspec to >>> ruby/rubyspec for clarity. >>> >>> >> --047d7b3a9a847b5f90050fbf39f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Martin,

I= t seems a known issue, but I think it is possible to fix.
Could yo= u run with the specdoc formatter, like
$ mspec -fs
That s= hould show the examples which are blocking.

You should report = the bug on https://github.com/rub= y/mspec or https://github.= com/ruby/rubyspec.

Regards,
Benoit

On 23 February 2015 at 11:1= 6, "Martin J. D=C3=BCrst" <duerst@it.aoyama.ac.jp> wrote:
Hello Anthony,

Maybe you can help me. I'm frequently compiling CRuby trunk on cygwin, = and occasionally tried to run rubyspec (make test-rubyspec). However, I alw= ays get the same result: Some lines of textual output, then about 7 lines o= f mostly dots with a few Fs and an occasional E or two, and then the thing = hangs with a busy ruby executable, which I have to kill via the task manage= r (Ctrl-C doesn't help).

I'd like to be able to submit bug reports, either for the spec or for t= he implementation, but I don't know what's wrong where I get Fs, an= d I don't know which test produced an endless loop. I didn't get an= y help from http:/= /rubyspec.org/mspec/, but maybe that's the wrong place to look.

Regards,=C2=A0 =C2=A0Martin.

On 2015/02/17 22:16, Anthony Crumley wrote:
Beniot,

I have been working on reconciling RubySpec with the 2.x MRI versions over<= br> the last month.=C2=A0 https://github.com/anthonycrumley= /rubyspec/commits/master

My intention is to:
1) Get RubySpec updated to run with all the 2.x versions of MRI.
2) Get the nurse/rubyspec updates since the fork added.
3) Get the updated RubySpecs into the MRI CI.
4) Hopefully find that repo a home at either rubyspec/rubyspec or
ruby/rubyspec.

I agree with you that the RubySpec tests are very valuable and would LOVE to work with you on them.

Anthony

On Tue Feb 17 2015 at 6:59:48 AM Benoit Daloze <eregontp@gmail.com> wrote:

On 17 February 2015 at 13:32, Benoit Daloze <eregontp@gmail.com> wrote:

- The second step is really to choose a canonical RubySpec repository, to avoid "death by too much forks".
This repository should only contain RubySpec tests for practical reasons. We should allow many specs contributors to take part in merging changes
and maintaining specs.
I think this was a fatal flaw of rubyspec/rubyspec in that too few people had the large burden of merging and maintaining the specs.

The main existing repository I see today is nurse/rubyspec.
I am thinking the process could be similar to handling pull requests on
ruby/ruby in that some contributors would provide feedback and merge them.<= br> The CI is very useful in this regard to ensure MRI is not broken
inadvertently.


I think it would make sense in that case to move nurse/rubyspec to
ruby/rubyspec for clarity.



--047d7b3a9a847b5f90050fbf39f0--