experimental branch: status update
Hi guys, I figured out that it would be a good idea to give periodical status updates on what's happening in the experimental branch, so here is the first one :) - The compiler is now able (AFAIK) to compile all the language specs, so I guess it's now roughly complete. - Lots of progresses on the RubySpecs - Eloy might want to comment here maybe :) - A third of the core/io specs are now passing too. Good progress on the IO front. - The `for' expression has been fixed (it was too unstable). - Lots of fixes in eval & dynamic variables. A preliminary version of Binding was implemented. The new dvar implementation is more or less twice faster than the previous one. - Better exception handling of top level exceptions. - Calling 'return' from a block has been implemented (but not optimized, yet). - Fixed the 'require of the death' bug (basically, requiring a file that requires another file that require the first file again). - Implemented implicit enumeratorization (Example: [1,2,3].each). - Ported old code to the new rb_objc_block_call() syntax (which is faster). - Implemented catch/throw. - Thanks to everything above, IRB is now running! $ ./miniruby -I./lib bin/irb irb: warn: can't alias exit from irb_exit. irb(main):001:0> 1+2 => 3 irb(main):002:0> x=40 => 40 irb(main):003:0> x+2 => 42 irb(main):004:0> def foo; 42; end => nil irb(main):005:0> foo => 42 irb(main):006:0> (With a few caveats: there are _lots_ of bugs around.) Starting IRB takes about 1.5 seconds on my machine, this is way to slow and we need to optimize this. So I will work on this. The compiler & JIT strategy have not been optimized yet. Next step will be to implement the BridgeSupport plumbing then we can bootstrap Cocoa again! Laurent
Hi, On Apr 6, 2009, at 10:47 AM, Laurent Sansonetti wrote:
Hi guys,
I figured out that it would be a good idea to give periodical status updates on what's happening in the experimental branch, so here is the first one :)
- The compiler is now able (AFAIK) to compile all the language specs, so I guess it's now roughly complete.
- Lots of progresses on the RubySpecs - Eloy might want to comment here maybe :)
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code. If there are people who would like to work on getting examples up-to- date, please respond and I will try to give you an outline on a workflow. If you just want to run the specs use the spec:ci task. One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
- Thanks to everything above, IRB is now running!
Shweet! :-) - Eloy
On Apr 06, 2009, at 04:16, Eloy Duran wrote:
Hi,
On Apr 6, 2009, at 10:47 AM, Laurent Sansonetti wrote:
Hi guys,
I figured out that it would be a good idea to give periodical status updates on what's happening in the experimental branch, so here is the first one :)
- The compiler is now able (AFAIK) to compile all the language specs, so I guess it's now roughly complete.
- Lots of progresses on the RubySpecs - Eloy might want to comment here maybe :)
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code.
If there are people who would like to work on getting examples up-to- date, please respond and I will try to give you an outline on a workflow.
If you just want to run the specs use the spec:ci task.
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I am assuming the spec:ci task uses miniruby to run the tests currently, and will use miniruby or macruby in the future. Why not make a new task spec:ci32 that forces 32-bit execution on 64- bit machines using `arch -arch i386 miniruby` instead of `miniruby`? Just an idea.
- Thanks to everything above, IRB is now running!
Shweet! :-)
- Eloy _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code.
If there are people who would like to work on getting examples up- to-date, please respond and I will try to give you an outline on a workflow.
If you just want to run the specs use the spec:ci task.
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I am assuming the spec:ci task uses miniruby to run the tests currently, and will use miniruby or macruby in the future.
Why not make a new task spec:ci32 that forces 32-bit execution on 64- bit machines using `arch -arch i386 miniruby` instead of `miniruby`?
Just an idea.
The question is not on how to circumvent these failures, rather the question is _if_ these failures don't occur on 32 bit machines. Laurent and I both only have 64 bit these machines and we see these failures, whereas Patrick who apparently has a 32 bit machine does not see them. The specs should ultimately pass on both archs, so we'd like feedback from other people on 32 bit on whether or not they see these failures. Eloy
On Apr 06, 2009, at 07:50, Eloy Duran wrote:
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code.
If there are people who would like to work on getting examples up- to-date, please respond and I will try to give you an outline on a workflow.
If you just want to run the specs use the spec:ci task.
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I am assuming the spec:ci task uses miniruby to run the tests currently, and will use miniruby or macruby in the future.
Why not make a new task spec:ci32 that forces 32-bit execution on 64-bit machines using `arch -arch i386 miniruby` instead of `miniruby`?
Just an idea.
The question is not on how to circumvent these failures, rather the question is _if_ these failures don't occur on 32 bit machines. Laurent and I both only have 64 bit these machines and we see these failures, whereas Patrick who apparently has a 32 bit machine does not see them.
The specs should ultimately pass on both archs, so we'd like feedback from other people on 32 bit on whether or not they see these failures.
Eloy _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sorry I only meant to suggest this to aid in testing as you suggest. By adding a second task spec:ci32 that forces 32-bit execution of tests you and Laurent could see if the problem goes away when running the 32-bit code, even on a 64-bit machine. Hopefully if it works for Patrick and is tied to 32-bit it is tied to the code and not to the hardware, in which case spec:ci would still fail on your machine and spec:ci32 would work, which would then hopefully help isolate the problem with 64-bit. This also means spec could become a task that could test to see what kind of machine you are on, if you are on a 32-bit machine just run spec:ci, if you are on a 64-bit machine run spec:ci and spec:ci32 so that the 32-bit build always gets tested. Hope that makes more sense now. Jordan
Ah, on that bike! (Which is a direct translation of a Dutch saying meaning basically just "Aha!" ;-) ) Yes that sounds like an excellent idea, will do. Thanks, Eloy On Apr 6, 2009, at 2:54 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 07:50, Eloy Duran wrote:
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code.
If there are people who would like to work on getting examples up- to-date, please respond and I will try to give you an outline on a workflow.
If you just want to run the specs use the spec:ci task.
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I am assuming the spec:ci task uses miniruby to run the tests currently, and will use miniruby or macruby in the future.
Why not make a new task spec:ci32 that forces 32-bit execution on 64-bit machines using `arch -arch i386 miniruby` instead of `miniruby`?
Just an idea.
The question is not on how to circumvent these failures, rather the question is _if_ these failures don't occur on 32 bit machines. Laurent and I both only have 64 bit these machines and we see these failures, whereas Patrick who apparently has a 32 bit machine does not see them.
The specs should ultimately pass on both archs, so we'd like feedback from other people on 32 bit on whether or not they see these failures.
Eloy _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sorry I only meant to suggest this to aid in testing as you suggest. By adding a second task spec:ci32 that forces 32-bit execution of tests you and Laurent could see if the problem goes away when running the 32-bit code, even on a 64-bit machine. Hopefully if it works for Patrick and is tied to 32-bit it is tied to the code and not to the hardware, in which case spec:ci would still fail on your machine and spec:ci32 would work, which would then hopefully help isolate the problem with 64-bit.
This also means spec could become a task that could test to see what kind of machine you are on, if you are on a 32-bit machine just run spec:ci, if you are on a 64-bit machine run spec:ci and spec:ci32 so that the 32-bit build always gets tested.
Hope that makes more sense now.
Jordan_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks, Eloy
After taking a quick look at the spec tasks and the way they run it might be easier to: 1) test for 64-bit enabled machines, if you are on a 32-bit machine build normally an run specs normally 2) ok you are on a 64-bit machine, during build make miniruby and miniruby32 (which can be made with lipo from miniruby, something like `lipo -extract i386 -output miniruby 32 miniruby`) 3) have spec now point to spec:ci and spec:ci32 on 64-bit machines 4) have the individual tasks like spec:partially_green also have a 32- bit version of themselves BTW, some of the tasks like spec:ci currently run mspec/bin/mspec which has a run line of "#!/usr/bin/env ruby". To override this shouldn't mspec/bin/mspec always get called as `./miniruby{,32} -I./ lib mspec/bin/mspec` for MacRuby testing? Just curious. Jordan
On Apr 6, 2009, at 2:54 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 07:50, Eloy Duran wrote:
As Laurent noted we are now passing most language specs. The ones that we don't pass yet are either because we simply fail, or these examples (tests) are simply not updated for Ruby 1.9 yet. Which as you all know is what MacRuby is based on. This is an area where all of you Ruby devs can help out if you feel the need to get MacRuby up and running asap but don't want to work on the C(++) code.
If there are people who would like to work on getting examples up-to-date, please respond and I will try to give you an outline on a workflow.
If you just want to run the specs use the spec:ci task.
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I am assuming the spec:ci task uses miniruby to run the tests currently, and will use miniruby or macruby in the future.
Why not make a new task spec:ci32 that forces 32-bit execution on 64-bit machines using `arch -arch i386 miniruby` instead of `miniruby`?
Just an idea.
The question is not on how to circumvent these failures, rather the question is _if_ these failures don't occur on 32 bit machines. Laurent and I both only have 64 bit these machines and we see these failures, whereas Patrick who apparently has a 32 bit machine does not see them.
The specs should ultimately pass on both archs, so we'd like feedback from other people on 32 bit on whether or not they see these failures.
Eloy _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Sorry I only meant to suggest this to aid in testing as you suggest. By adding a second task spec:ci32 that forces 32-bit execution of tests you and Laurent could see if the problem goes away when running the 32-bit code, even on a 64-bit machine. Hopefully if it works for Patrick and is tied to 32-bit it is tied to the code and not to the hardware, in which case spec:ci would still fail on your machine and spec:ci32 would work, which would then hopefully help isolate the problem with 64-bit.
This also means spec could become a task that could test to see what kind of machine you are on, if you are on a 32-bit machine just run spec:ci, if you are on a 64-bit machine run spec:ci and spec:ci32 so that the 32-bit build always gets tested.
Hope that makes more sense now.
Jordan_______________________________________________ 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
On Apr 6, 2009, at 3:28 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks, Eloy
After taking a quick look at the spec tasks and the way they run it might be easier to:
1) test for 64-bit enabled machines, if you are on a 32-bit machine build normally an run specs normally
2) ok you are on a 64-bit machine, during build make miniruby and miniruby32 (which can be made with lipo from miniruby, something like `lipo -extract i386 -output miniruby 32 miniruby`)
3) have spec now point to spec:ci and spec:ci32 on 64-bit machines
4) have the individual tasks like spec:partially_green also have a 32-bit version of themselves
Creating a separate miniruby is of course an option, although I'm not sure it would be needed. Why did you come to this conclusion?
BTW, some of the tasks like spec:ci currently run mspec/bin/mspec which has a run line of "#!/usr/bin/env ruby". To override this shouldn't mspec/bin/mspec always get called as `./miniruby{,32} -I./ lib mspec/bin/mspec` for MacRuby testing? Just curious.
Ah yes, this is because ./mspec/bin/mspec is a frontend script to the various runners, such as ./mspec/bin/mspec-ci and ./mspec/bin/mspec-run. Based on the --target given to mspec the runners will be ran with the correct bin. In our case the target, ./miniruby, is set by the ./spec/frozen/ macruby.mspec script. So to run the same set of selected specs on a different ruby you just use the correct mspec config script, for instance ./spec/frozen/ruby.1.9.mspec or give the --target option as r19 to ./mspec/bin/mspec I hope this was a bit clear? Eloy
On Apr 06, 2009, at 08:40, Eloy Duran wrote:
On Apr 6, 2009, at 3:28 PM, Jordan Breeding wrote:
On Apr 06, 2009, at 08:09, Eloy Duran wrote:
Ah, on that bike! (Which is a direct translation of a Dutch saying meaning basically just "Aha!" ;-) )
Yes that sounds like an excellent idea, will do.
Thanks, Eloy
After taking a quick look at the spec tasks and the way they run it might be easier to:
1) test for 64-bit enabled machines, if you are on a 32-bit machine build normally an run specs normally
2) ok you are on a 64-bit machine, during build make miniruby and miniruby32 (which can be made with lipo from miniruby, something like `lipo -extract i386 -output miniruby 32 miniruby`)
3) have spec now point to spec:ci and spec:ci32 on 64-bit machines
4) have the individual tasks like spec:partially_green also have a 32-bit version of themselves
Creating a separate miniruby is of course an option, although I'm not sure it would be needed. Why did you come to this conclusion?
Because I don't know if gdb places nice with `arch -arch i386` but you can definitely do `gdb ./miniruby32`
BTW, some of the tasks like spec:ci currently run mspec/bin/mspec which has a run line of "#!/usr/bin/env ruby". To override this shouldn't mspec/bin/mspec always get called as `./miniruby{,32} -I./ lib mspec/bin/mspec` for MacRuby testing? Just curious.
Ah yes, this is because ./mspec/bin/mspec is a frontend script to the various runners, such as ./mspec/bin/mspec-ci and ./mspec/bin/ mspec-run. Based on the --target given to mspec the runners will be ran with the correct bin.
In our case the target, ./miniruby, is set by the ./spec/frozen/ macruby.mspec script. So to run the same set of selected specs on a different ruby you just use the correct mspec config script, for instance ./spec/frozen/ruby.1.9.mspec or give the --target option as r19 to ./mspec/bin/mspec
I hope this was a bit clear?
Eloy
Yeah, that makes it clearer, so there would need to be a way to make sure that for regular tasks like spec:ci the runner still just gets set to ./miniruby, but for new tasks like spec:ci32 it should get set to either `./miniruby32` or `arch -arch i386 ./miniruby`.
1) test for 64-bit enabled machines, if you are on a 32-bit machine build normally an run specs normally
2) ok you are on a 64-bit machine, during build make miniruby and miniruby32 (which can be made with lipo from miniruby, something like `lipo -extract i386 -output miniruby 32 miniruby`)
3) have spec now point to spec:ci and spec:ci32 on 64-bit machines
4) have the individual tasks like spec:partially_green also have a 32-bit version of themselves
Creating a separate miniruby is of course an option, although I'm not sure it would be needed. Why did you come to this conclusion?
Because I don't know if gdb places nice with `arch -arch i386` but you can definitely do `gdb ./miniruby32`
BTW, some of the tasks like spec:ci currently run mspec/bin/mspec which has a run line of "#!/usr/bin/env ruby". To override this shouldn't mspec/bin/mspec always get called as `./miniruby{,32} - I./lib mspec/bin/mspec` for MacRuby testing? Just curious.
Ah yes, this is because ./mspec/bin/mspec is a frontend script to the various runners, such as ./mspec/bin/mspec-ci and ./mspec/bin/ mspec-run. Based on the --target given to mspec the runners will be ran with the correct bin.
In our case the target, ./miniruby, is set by the ./spec/frozen/ macruby.mspec script. So to run the same set of selected specs on a different ruby you just use the correct mspec config script, for instance ./spec/frozen/ruby.1.9.mspec or give the --target option as r19 to ./mspec/bin/mspec
I hope this was a bit clear?
Eloy
Yeah, that makes it clearer, so there would need to be a way to make sure that for regular tasks like spec:ci the runner still just gets set to ./miniruby, but for new tasks like spec:ci32 it should get set to either `./miniruby32` or `arch -arch i386 ./miniruby`.
Cool, I'll have a look tonight (or whenever) at if we even need a second binary or if there's some way to run the specs and also use for instance gdb. Eloy
On Mon, Apr 6, 2009 at 10:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
If there are people who would like to work on getting examples up-to-date, please respond and I will try to give you an outline on a workflow.
I'd be interested in helping out, but atm I'm not up to speed enough to have even built the experimental branch. Cheers, Chris
Hi Chris, I've finally had some time to write an explanation on how to work on the specs. You can find it in spec/README.rdoc, or view it at: http://github.com/alloy/mr-experimental/blob/master/spec/README.rdoc Let me know if there are any questions, I probably left out important parts ;-) Cheers, Eloy On 6 apr 2009, at 17:39, Chris McGrath wrote:
On Mon, Apr 6, 2009 at 10:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
If there are people who would like to work on getting examples up- to-date, please respond and I will try to give you an outline on a workflow.
I'd be interested in helping out, but atm I'm not up to speed enough to have even built the experimental branch.
Cheers,
Chris _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I have a first generation MacBook Pro. $ svn up ... $ rake ... $ rake spec:ci (in /Users/blowmage/Scratch/macruby-experimental) ./mspec/bin/mspec ci -B ./spec/frozen/macruby.mspec spec/frozen/language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/frozen/core/io/inspect_spec.rb spec/frozen/core/io/initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/to_io_spec.rb spec/frozen/core/io/initialize_spec.rb MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, i386] ...........................................F......................... 1) The throw keyword does not convert strings to a symbol FAILED Expected ArgumentError but no exception was raised Finished in 9.338692 seconds 69 files, 672 examples, 1593 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/frozen/macr...] (See full trace by running task with --trace)
Hmm, so it's indeed a 32/64 bit issue. Thanks for trying Mike! - Eloy On 6 apr 2009, at 18:56, Mike Moore wrote:
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I have a first generation MacBook Pro.
$ svn up ... $ rake ... $ rake spec:ci (in /Users/blowmage/Scratch/macruby-experimental) ./mspec/bin/mspec ci -B ./spec/frozen/macruby.mspec spec/frozen/ language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/ closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/ core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/ frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/ frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/ frozen/core/io/inspect_spec.rb spec/frozen/core/io/ initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/frozen/ core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/ frozen/core/io/syswrite_spec.rb spec/frozen/core/io/tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/to_io_spec.rb spec/frozen/core/io/initialize_spec.rb MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, i386] ...........................................F.........................
1) The throw keyword does not convert strings to a symbol FAILED Expected ArgumentError but no exception was raised
Finished in 9.338692 seconds
69 files, 672 examples, 1593 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/ frozen/macr...]
(See full trace by running task with --trace) _______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Based on that I would say that it is a good idea going forward to try having 64-bit machines run tests in 64-bit and 32-bit mode. I look forward to seeing any solution to running the tests in 32-bit mode that you come up with. Jordan On Apr 06, 2009, at 13:07, Eloy Duran wrote:
Hmm, so it's indeed a 32/64 bit issue.
Thanks for trying Mike!
- Eloy
On 6 apr 2009, at 18:56, Mike Moore wrote:
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I have a first generation MacBook Pro.
$ svn up ... $ rake ... $ rake spec:ci (in /Users/blowmage/Scratch/macruby-experimental) ./mspec/bin/mspec ci -B ./spec/frozen/macruby.mspec spec/frozen/ language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/ closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/ core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/ frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/ frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/ frozen/core/io/inspect_spec.rb spec/frozen/core/io/ initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/ frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/ tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/ to_io_spec.rb spec/frozen/core/io/initialize_spec.rb MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, i386] ...........................................F.........................
1) The throw keyword does not convert strings to a symbol FAILED Expected ArgumentError but no exception was raised
Finished in 9.338692 seconds
69 files, 672 examples, 1593 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/ frozen/macr...]
(See full trace by running task with --trace) _______________________________________________ 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 just added a spec:ci32 task which will run the specs in 32 bit mode. It uses a simple script (miniruby32) which runs miniruby through /usr/ bin/arch. http://github.com/alloy/mr-experimental/commit/321cc9b0ae0acce82bdb59bdc11e4... And indeed :) % rake spec:ci32 (in /Users/eloy/Documents/DEVELOPMENT/MacRuby/git-svn-roxor) ./miniruby32 ./mspec/bin/mspec-ci -B ./spec/frozen/macruby.mspec spec/ frozen/language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/ io/closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/ core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/ frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/ frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/frozen/ core/io/inspect_spec.rb spec/frozen/core/io/initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/ frozen/core/io/to_io_spec.rb spec/frozen/core/io/initialize_spec.rb ..................................................................... Finished in 8.402635 seconds 69 files, 676 examples, 1600 expectations, 0 failures, 0 errors Cheers, Eloy On 6 apr 2009, at 22:52, Jordan Breeding wrote:
Based on that I would say that it is a good idea going forward to try having 64-bit machines run tests in 64-bit and 32-bit mode. I look forward to seeing any solution to running the tests in 32-bit mode that you come up with.
Jordan
On Apr 06, 2009, at 13:07, Eloy Duran wrote:
Hmm, so it's indeed a 32/64 bit issue.
Thanks for trying Mike!
- Eloy
On 6 apr 2009, at 18:56, Mike Moore wrote:
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran <eloy.de.enige@gmail.com> wrote:
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I have a first generation MacBook Pro.
$ svn up ... $ rake ... $ rake spec:ci (in /Users/blowmage/Scratch/macruby-experimental) ./mspec/bin/mspec ci -B ./spec/frozen/macruby.mspec spec/frozen/ language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/ closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/ core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/ frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/frozen/core/io/inspect_spec.rb spec/frozen/core/io/ initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/ frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/ tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/ to_io_spec.rb spec/frozen/core/io/initialize_spec.rb MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, i386] ...........................................F .........................
1) The throw keyword does not convert strings to a symbol FAILED Expected ArgumentError but no exception was raised
Finished in 9.338692 seconds
69 files, 672 examples, 1593 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/ frozen/macr...]
(See full trace by running task with --trace) _______________________________________________ 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
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
slightly out topic: w00t!! great job guys! - Matt 2009/4/7 Eloy Duran <eloy.de.enige@gmail.com>
Hi, I just added a spec:ci32 task which will run the specs in 32 bit mode. It uses a simple script (miniruby32) which runs miniruby through /usr/bin/arch.
http://github.com/alloy/mr-experimental/commit/321cc9b0ae0acce82bdb59bdc11e4...
And indeed :)
% rake spec:ci32 (in /Users/eloy/Documents/DEVELOPMENT/MacRuby/git-svn-roxor) ./miniruby32 ./mspec/bin/mspec-ci -B ./spec/frozen/macruby.mspec spec/frozen/language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/frozen/core/io/inspect_spec.rb spec/frozen/core/io/initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/to_io_spec.rb spec/frozen/core/io/initialize_spec.rb .....................................................................
Finished in 8.402635 seconds
69 files, 676 examples, 1600 expectations, 0 failures, 0 errors
Cheers, Eloy
On 6 apr 2009, at 22:52, Jordan Breeding wrote:
Based on that I would say that it is a good idea going forward to try having 64-bit machines run tests in 64-bit and 32-bit mode. I look forward to seeing any solution to running the tests in 32-bit mode that you come up with. Jordan
On Apr 06, 2009, at 13:07, Eloy Duran wrote:
Hmm, so it's indeed a 32/64 bit issue.
Thanks for trying Mike! - Eloy
On 6 apr 2009, at 18:56, Mike Moore wrote:
On Mon, Apr 6, 2009 at 3:16 AM, Eloy Duran <eloy.de.enige@gmail.com>wrote:
One last question I have for everyone on the list. If there's someone with a 32 bit intel machine, could you please please run the spec:ci task and see if you get any failures? It seems that, at least, because of a 32/64 bit issue some IO specs are now failing on my machines and those of Laurent. Thanks in advance!
I have a first generation MacBook Pro.
$ svn up ... $ rake ... $ rake spec:ci (in /Users/blowmage/Scratch/macruby-experimental) ./mspec/bin/mspec ci -B ./spec/frozen/macruby.mspec spec/frozen/language spec/frozen/core/io/binmode_spec.rb spec/frozen/core/io/closed_spec.rb spec/frozen/core/io/constants_spec.rb spec/frozen/core/io/each_byte_spec.rb spec/frozen/core/io/fileno_spec.rb spec/frozen/core/io/fsync_spec.rb spec/frozen/core/io/flush_spec.rb spec/frozen/core/io/getc_spec.rb spec/frozen/core/io/io_spec.rb spec/frozen/core/io/inspect_spec.rb spec/frozen/core/io/initialize_copy_spec.rb spec/frozen/core/io/putc_spec.rb spec/frozen/core/io/readchar_spec.rb spec/frozen/core/io/sync_spec.rb spec/frozen/core/io/syswrite_spec.rb spec/frozen/core/io/tell_spec.rb spec/frozen/core/io/to_i_spec.rb spec/frozen/core/io/to_io_spec.rb spec/frozen/core/io/initialize_spec.rb MacRuby version 0.5 (ruby 1.9.0) [universal-darwin9.0, i386] ...........................................F.........................
1) The throw keyword does not convert strings to a symbol FAILED Expected ArgumentError but no exception was raised
Finished in 9.338692 seconds
69 files, 672 examples, 1593 expectations, 1 failure, 0 errors rake aborted! Command failed with status (1): [./mspec/bin/mspec ci -B ./spec/frozen/macr...]
(See full trace by running task with --trace) _______________________________________________ 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
_______________________________________________ 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 (6)
-
Chris McGrath
-
Eloy Duran
-
Jordan Breeding
-
Laurent Sansonetti
-
Matt Aimonetti
-
Mike Moore