I'm an old crusty C programmer. I have a masters in CS and my focus was languages and compilers. MacRuby and LLVM are really exciting to me. I use a Mac. Working with Ruby since 2006. Love Rails. etc etc. I saw a previous thread in the archive where a newbie wanted to help and the reply was to help with testing. Thats fine. I'm worried about duplicate effort . Maybe split off some bugs / test cases I can work on? Most of my work will be during the weekends but I think I'd like to start setting things up during this week. Take care, Perry Ease Software, Inc. ( http://www.easesoftware.com ) Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems
Hi Perry, I wouldn't worry too much about duplicate efforts, there aren't many people working on the core itself. What you could do to start out, is to run the rubyspecs in spec/frozen/ language, as they should all run iirc, but there are some tagged ones. To run spec all which are tagged as failing: ./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./spec/ frozen/language --format spec (Actually, right now there's one causing a segfault.) You can then verify that the spec is valid for 1.9.x (HEAD), if not it should be updated, if it is then MacRuby should be fixed. I think this is a great way to start on the C parts of MacRuby. Besides the fails tag there are also specs tagged as critical, which will segfault etc. So there's actually a nice list of places that need to be fixed :) Be sure to check out the mspec-tag script to list all tagged specs. HTH, Eloy On 29 jun 2009, at 15:46, Perry Smith wrote:
I'm an old crusty C programmer. I have a masters in CS and my focus was languages and compilers. MacRuby and LLVM are really exciting to me. I use a Mac. Working with Ruby since 2006. Love Rails. etc etc.
I saw a previous thread in the archive where a newbie wanted to help and the reply was to help with testing. Thats fine. I'm worried about duplicate effort . Maybe split off some bugs / test cases I can work on? Most of my work will be during the weekends but I think I'd like to start setting things up during this week.
Take care, Perry Ease Software, Inc. ( http://www.easesoftware.com )
Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi, I'm not sure if you want this traffic on the list. I got everything compiled, etc. Ran the command below and captured the output. As you mentioned, there is a segment fault. I installed ruby 1.9.1p129 and changed the command below and added a - t /usr/local/bin/ruby after the -B <config> option and that got the same run with Ruby 1.9. It has various failures. The test that faults is:
The return keyword in a Thread - raises a LocalJumpError if used to exit a thread
It passes Ruby 1.9 so I thought I would dig into that test first. Does that sound good? Perry Ease Software, Inc. ( http://www.easesoftware.com ) Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems On Jun 29, 2009, at 9:49 AM, Eloy Duran wrote:
Hi Perry,
I wouldn't worry too much about duplicate efforts, there aren't many people working on the core itself. What you could do to start out, is to run the rubyspecs in spec/ frozen/language, as they should all run iirc, but there are some tagged ones.
To run spec all which are tagged as failing:
./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./ spec/frozen/language --format spec
(Actually, right now there's one causing a segfault.)
You can then verify that the spec is valid for 1.9.x (HEAD), if not it should be updated, if it is then MacRuby should be fixed. I think this is a great way to start on the C parts of MacRuby.
Besides the fails tag there are also specs tagged as critical, which will segfault etc. So there's actually a nice list of places that need to be fixed :) Be sure to check out the mspec-tag script to list all tagged specs.
HTH, Eloy
On 29 jun 2009, at 15:46, Perry Smith wrote:
I'm an old crusty C programmer. I have a masters in CS and my focus was languages and compilers. MacRuby and LLVM are really exciting to me. I use a Mac. Working with Ruby since 2006. Love Rails. etc etc.
I saw a previous thread in the archive where a newbie wanted to help and the reply was to help with testing. Thats fine. I'm worried about duplicate effort . Maybe split off some bugs / test cases I can work on? Most of my work will be during the weekends but I think I'd like to start setting things up during this week.
Take care, Perry Ease Software, Inc. ( http://www.easesoftware.com )
Low cost SATA Disk Systems for IBMs p5, pSeries, and RS/6000 AIX systems
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Hi,
I'm not sure if you want this traffic on the list.
Sure no problem, it's not that we that much traffic yet :)
I got everything compiled, etc. Ran the command below and captured the output. As you mentioned, there is a segment fault.
I installed ruby 1.9.1p129 and changed the command below and added a -t /usr/local/bin/ruby after the -B <config> option and that got the same run with Ruby 1.9. It has various failures.
The version of 1.9 that should be used for the specs and MacRuby is trunk HEAD. Which means it's quite the moving target stil. However, when working on MacRuby it should be a big problem. But the main thing is that both MacRuby and RubySpec have not set a fixed target yet for 1.9 compatibility.
The test that faults is:
The return keyword in a Thread - raises a LocalJumpError if used to exit a thread
It passes Ruby 1.9 so I thought I would dig into that test first.
Does that sound good?
That sounds great! But please first double-check with 1.9 HEAD, if the spec still passes on that version, then yes, please look into it and/ or fix MacRuby. Thanks! Eloy
That sounds great! But please first double-check with 1.9 HEAD, if the spec still passes on that version, then yes, please look into it and/or fix MacRuby.
I tested with the trunk and it passes too. Is this the way to run a single test? ./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./spec/ frozen/language/return_spec.rb --format spec Doing this way, the test that seg faults normally just errors out and then a few tests later we get a seg fault. I wanted to check and be sure the way I'm testing is right. Thanks, Perry
That sounds great! But please first double-check with 1.9 HEAD, if the spec still passes on that version, then yes, please look into it and/or fix MacRuby.
Hey, sorry to be a pest but my question about how to run a single test never got answered. That would help save me some time: I tested with the trunk and it passes too. Is this the way to run a single test? ./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./spec/ frozen/language/return_spec.rb --format spec Doing this way, the test that seg faults normally just errors out and then a few tests later we get a seg fault. I wanted to check and be sure the way I'm testing is right. Thanks, Perry
On Fri, Jul 3, 2009 at 9:30 AM, Perry Smith <pedzsan@gmail.com> wrote:
Hey, sorry to be a pest but my question about how to run a single test never got answered. That would help save me some time:
I tested with the trunk and it passes too.
Is this the way to run a single test?
./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./spec/frozen/language/return_spec.rb --format spec
Doing this way, the test that seg faults normally just errors out and then a few tests later we get a seg fault.
I wanted to check and be sure the way I'm testing is right.
Thanks, Perry
Hi Perry, It's not entirely clear to me if the question you're asking pertains to the best way to run specs for MacRuby, running a focused test under MSpec, or both. If you're looking for the latter, check out the -p and -e options. They allow you to run only those tests whose descriptions match a regexp or string. E.g. ./mspec/bin/mspec run -B spec/macruby.mspec spec/frozen/language/for_spec.rb -p 'splats multiple arguments' Not quite as simple as specifying a line number, but it should do the trick. HTH, Mike
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Ugh, sorry Perry. It seems I forgot to actually send my email... Anyways, Mike is correct. For more info on MSpec, and all the options for the runners, see: http://rubyspec.org/wiki/mspec Eloy On Jul 7, 2009, at 10:36 PM, Mike Sassak wrote:
On Fri, Jul 3, 2009 at 9:30 AM, Perry Smith <pedzsan@gmail.com> wrote:
Hey, sorry to be a pest but my question about how to run a single test never got answered. That would help save me some time:
I tested with the trunk and it passes too.
Is this the way to run a single test?
./mspec/bin/mspec run -I./lib -B ./spec/macruby.mspec -g fails ./ spec/frozen/language/return_spec.rb --format spec
Doing this way, the test that seg faults normally just errors out and then a few tests later we get a seg fault.
I wanted to check and be sure the way I'm testing is right.
Thanks, Perry
Hi Perry,
It's not entirely clear to me if the question you're asking pertains to the best way to run specs for MacRuby, running a focused test under MSpec, or both. If you're looking for the latter, check out the -p and -e options. They allow you to run only those tests whose descriptions match a regexp or string. E.g.
./mspec/bin/mspec run -B spec/macruby.mspec spec/frozen/language/ for_spec.rb -p 'splats multiple arguments'
Not quite as simple as specifying a line number, but it should do the trick.
HTH, Mike
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (3)
-
Eloy Duran
-
Mike Sassak
-
Perry Smith