Yup, we do "mspec.bat ci" (currently without the .bat) which is similar to
calling mspec-ci.bat.
Since irtests.rb spawns separate processes, its strange that things work if
Ivan runs the test suites individually manually, but not if irtests.rb does it
automatically (and individually). It could be some thread tests acting up.
Ivan, you could try running multiple instances of the thread tests ("mspec ci
-fs core\thread") in a loop overnight and see if it hangs or not. We have done
that and tagged such unstable tests with the "thread" tag (Jim chose that over
"unstable" for various reasons), but a different set of tests might be hanging
on Mono.
From: [email protected]
[mailto:[email protected]] On Behalf Of Jimmy Schementi
Sent: Thursday, August 06, 2009 3:51 PM
To: [email protected]
Subject: Re: [Ironruby-core] Problems running irtests.bat
Sounds like the same issue we had with the thread specs ... completing the run
but not terminating the process. Is "mspec ci" the equivalent of what we run on
checkin, or is it a further subset?
________________________________
From: [email protected] [[email protected]]
on behalf of Ivan Porto Carrero [[email protected]]
Sent: Thursday, August 06, 2009 3:33 PM
To: [email protected]
Subject: Re: [Ironruby-core] Problems running irtests.bat
It just doesn't fall through really
so it doesn't really hang but rather stalls or hibernates or something. I think
the process just doesn't exit after printing everything but it's also not doing
any work anymore.
The specs execute completely.
Apart from the smoke tests and legacy tests i can run all the tests in 2
blocks. I can run the specs and then I can run the rubygems, rake and yaml
tests but I have to choose which bit I want to run
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Fri, Aug 7, 2009 at 12:21 AM, Shri Borde
<[email protected]<mailto:[email protected]>> wrote:
What does happen after the 3rd set of ruby specs? Does irtests.rb exit or does
it hang? Are results printed out from the 3rd set of ruby specs?
You could try all the individual test tasks by themselves to isolate problems.
"rake -T" will show you all the available test tasks.
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Ivan Porto Carrero
Sent: Thursday, August 06, 2009 3:08 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [Ironruby-core] Problems running irtests.bat
for mono I use mspec-ci and that works..
but after it runs the 3rd set of ruby specs it won't continue to the rubygems
tests.
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)
On Thu, Aug 6, 2009 at 11:44 PM, Ryan Riley
<[email protected]<mailto:[email protected]>> wrote:
That's a good point, and I forgot to add the ".bat" to mspec in my original
email. And of course, that fixes the problem. :) I removed the full path and
just added ".bat" and I can run the tests just fine.
Ryan Riley
[email protected]<mailto:[email protected]>
http://panesofglass.org/
http://wizardsofsmart.net/
On Thu, Aug 6, 2009 at 4:24 PM, Shri Borde
<[email protected]<mailto:[email protected]>> wrote:
To add to that, running "mspec ci -fd :lang" worked from the command line. When
irtests.rb tried to call system() with that exact same command line (we
verified that it was the exact same value), system() failed returning false.
Doing system("where mspec") from within irtests.rb did show the correct version
of (mspec and) mspec.bat, which implies that the value of PATH of the "rake"
process was also correct.
Ryan, one thought just occurred to me. What happens if you do "mspec_base =
"mspec.bat ci -fd"""? ie. add ".bat". I wonder if system("mspec ci -fd") is
trying to run the "mspec" Ruby file.
In either case, using the full path sounds like a good idea anyway.
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Ryan Riley
Sent: Thursday, August 06, 2009 2:15 PM
To: [email protected]<mailto:[email protected]>
Subject: [Ironruby-core] Problems running irtests.bat
During our pair programming session today, Shri, Kevin, and I walked through
some issues running RubySpecs from irtests and rake test:spec_a. The issue
appears to have something to do with the path, as we tried numerous usages of
system with various commands. We finally solved it by adding mspec_path =
"#{root}\\..\\External.LCA_RESTRICTED\\Languages\\IronRuby\\mspec\\mspec\\bin"
and including mspec_path at the beginning of mspec_base =
"#{mspec_path}\\mspec.bat ci -fd", effectively hard-coding the path.
I believe Kevin also had this problem, so if anyone else is having the problem,
you can try that. After making those changes, everything ran fine for me.
Ryan Riley
[email protected]<mailto:[email protected]>
http://panesofglass.org/
http://wizardsofsmart.net/
_______________________________________________
Ironruby-core mailing list
[email protected]<mailto:[email protected]>
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
[email protected]<mailto:[email protected]>
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
[email protected]<mailto:[email protected]>
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core
