SVN r118 and RubySpec integration

I just pushed SVN r118 out which contains RubySpec integration. There
are a few things that you’ll need to do:

  1.   (Optional) get a GitHub account (http://github.com)
    
  2.   (Optional) install GIT:
    

a. Goto the msysgit project and download the .exe based installer:
http://code.google.com/p/msysgit/

b. Make sure in the GIT setup that you click on the radio button
labeled “Run Git from the Windows Command Prompt”

c. Restart your command prompt

  1.   Navigate to my page: http://github.com/jflam to see the three 
    

GIT projects that you’ll need to clone: ironruby-tags, mspec, and
rubyspec. mspec and rubyspec are forks of the main projects so that we
can add IronRuby specific tests and potential changes to mspec. The
RubySpec committers can pull from these repositories to incorporate our
changes. ironruby-tags is a project that contains the list of rubyspec
specs that we currently exclude to get a clean regression baseline.

  1.   If you have GIT installed, create a directory to hold these 
    

projects. I use %USERPROFILE%\dev:

a. in ~\dev\ironruby-tags run: git clone
git://github.com/jflam/ironruby-tags.git

b. in ~\dev\mspec run: git clone git://github.com/jflam/mspec.git

c. in ~\dev\rubyspec run: git clone
git://github.com/jflam/rubyspec.git

  1.   If you don't have GIT installed (and why don't you??? :)) you 
    

can download the tarball using the download button in each project.

Once you have those projects in place, you’ll need to grab r118 from
RubyForge. There’s a file in \trunk called runfirst.cmd. This will
enable skip verification for projects signed with our public key, and it
will create a default configuration file at %USERPROFILE%.irconfig.rb.

If you followed my instructions and created
%USERPROFILE%\dev[ironruby-tags,mspec,rubyspec] you’re good to go. If
you didn’t, you’ll need to edit the paths in .irconfig.rb

You can test your setup by running the new regression test baseline rake
task:

rake regression

This should report 0 failures and 0 errors.

This is the first test of this stuff outside of my machine, so please
kick the tires!

Thanks,
-John

Next thing:

I changed the place that the cloned GIT repos were held and on compile I
get
these warnings:

D:\dev\ruby\ironruby\head>rake compile

(in D:/dev/ruby/ironruby/head)

C:\Documents and Settings\pete/.irconfig.rb:19: warning: already
initialized
constant TAGS

C:\Documents and Settings\pete/.irconfig.rb:20: warning: already
initialized
constant RUBYSPEC

C:\Documents and Settings\pete/.irconfig.rb:21: warning: already
initialized
constant MSPEC

I appreciate that this should not be a problem but could be tidied up?

Pete

From: [email protected]
[mailto:[email protected]] On Behalf Of John L.
(IRONRUBY)
Sent: Tuesday,01 July 01, 2008 00:59
To: [email protected]
Subject: [Ironruby-core] SVN r118 and RubySpec integration

I just pushed SVN r118 out which contains RubySpec integration. There
are a
few things that you’ll need to do:

  1.   (Optional) get a GitHub account (http://github.com)
    
  2.   (Optional) install GIT:
    

a. Goto the msysgit project and download the .exe based installer:
http://code.google.com/p/msysgit/

b. Make sure in the GIT setup that you click on the radio button
labeled “Run Git from the Windows Command Prompt”

c. Restart your command prompt

  1.   Navigate to my page: http://github.com/jflam to see the three 
    

GIT
projects that you’ll need to clone: ironruby-tags, mspec, and rubyspec.
mspec and rubyspec are forks of the main projects so that we can add
IronRuby specific tests and potential changes to mspec. The RubySpec
committers can pull from these repositories to incorporate our changes.
ironruby-tags is a project that contains the list of rubyspec specs that
we
currently exclude to get a clean regression baseline.

  1.   If you have GIT installed, create a directory to hold these
    

projects. I use %USERPROFILE%\dev:

a. in ~\dev\ironruby-tags run: git clone
git://github.com/jflam/ironruby-tags.git

b. in ~\dev\mspec run: git clone git://github.com/jflam/mspec.git

c. in ~\dev\rubyspec run: git clone
git://github.com/jflam/rubyspec.git

  1.   If you don't have GIT installed (and why don't you??? J) you 
    

can
download the tarball using the download button in each project.

Once you have those projects in place, you’ll need to grab r118 from
RubyForge. There’s a file in \trunk called runfirst.cmd. This will
enable
skip verification for projects signed with our public key, and it will
create a default configuration file at %USERPROFILE%.irconfig.rb.

If you followed my instructions and created
%USERPROFILE%\dev[ironruby-tags,mspec,rubyspec] you’re good to go. If
you
didn’t, you’ll need to edit the paths in .irconfig.rb

You can test your setup by running the new regression test baseline rake
task:

rake regression

This should report 0 failures and 0 errors.

This is the first test of this stuff outside of my machine, so please
kick
the tires!

Thanks,

-John

First thing to note:

D:\dev\ruby\ironruby\head>runfirst.cmd

D:\dev\ruby\ironruby\head>sn -Vr *,31bf3856ad364e35

Microsoft (R) .NET Framework Strong Name Utility Version 3.5.21022.8

Copyright (c) Microsoft Corporation. All rights reserved.

Verification entry added for assembly ‘*,31bf3856ad364e35’

D:\dev\ruby\ironruby\head>copy default.irconfig.rb C:\Documents and
Settings\pete.irconfig.rb

The syntax of the command is incorrect.

The line that copies the .irconfig.rb file in runfirst.cmd needs quotes
around the “to” parameter of “copy”:

copy default.irconfig.rb “%USERPROFILE%.irconfig.rb”

Pete

From: [email protected]
[mailto:[email protected]] On Behalf Of John L.
(IRONRUBY)
Sent: Tuesday,01 July 01, 2008 00:59
To: [email protected]
Subject: [Ironruby-core] SVN r118 and RubySpec integration

I just pushed SVN r118 out which contains RubySpec integration. There
are a
few things that you’ll need to do:

  1.   (Optional) get a GitHub account (http://github.com)
    
  2.   (Optional) install GIT:
    

a. Goto the msysgit project and download the .exe based installer:
http://code.google.com/p/msysgit/

b. Make sure in the GIT setup that you click on the radio button
labeled “Run Git from the Windows Command Prompt”

c. Restart your command prompt

  1.   Navigate to my page: http://github.com/jflam to see the three 
    

GIT
projects that you’ll need to clone: ironruby-tags, mspec, and rubyspec.
mspec and rubyspec are forks of the main projects so that we can add
IronRuby specific tests and potential changes to mspec. The RubySpec
committers can pull from these repositories to incorporate our changes.
ironruby-tags is a project that contains the list of rubyspec specs that
we
currently exclude to get a clean regression baseline.

  1.   If you have GIT installed, create a directory to hold these
    

projects. I use %USERPROFILE%\dev:

a. in ~\dev\ironruby-tags run: git clone
git://github.com/jflam/ironruby-tags.git

b. in ~\dev\mspec run: git clone git://github.com/jflam/mspec.git

c. in ~\dev\rubyspec run: git clone
git://github.com/jflam/rubyspec.git

  1.   If you don't have GIT installed (and why don't you??? J) you 
    

can
download the tarball using the download button in each project.

Once you have those projects in place, you’ll need to grab r118 from
RubyForge. There’s a file in \trunk called runfirst.cmd. This will
enable
skip verification for projects signed with our public key, and it will
create a default configuration file at %USERPROFILE%.irconfig.rb.

If you followed my instructions and created
%USERPROFILE%\dev[ironruby-tags,mspec,rubyspec] you’re good to go. If
you
didn’t, you’ll need to edit the paths in .irconfig.rb

You can test your setup by running the new regression test baseline rake
task:

rake regression

This should report 0 failures and 0 errors.

This is the first test of this stuff outside of my machine, so please
kick
the tires!

Thanks,

-John

And finally when I run rake regression I get a suspiciously quick
result:

D:\dev\ruby\ironruby\head>rake regression

(in D:/dev/ruby/ironruby/head)

C:\Documents and Settings\pete/.irconfig.rb:19: warning: already
initialized
constant TAGS

C:\Documents and Settings\pete/.irconfig.rb:20: warning: already
initialized
constant RUBYSPEC

C:\Documents and Settings\pete/.irconfig.rb:21: warning: already
initialized
constant MSPEC

Summary:

0 types, 0 files, 0 examples, 0 expectations, 0 failures, 0 errors

Nothing seems to be getting run? If I run rake spec then it does run
the
tests:

D:\dev\ruby\ironruby\head>rake spec

(in D:/dev/ruby/ironruby/head)

C:\Documents and Settings\pete/.irconfig.rb:19: warning: already
initialized
constant TAGS

C:\Documents and Settings\pete/.irconfig.rb:20: warning: already
initialized
constant RUBYSPEC

C:\Documents and Settings\pete/.irconfig.rb:21: warning: already
initialized
constant MSPEC

2199 examples, 0 failures

0

Is this what is expected?

Pete

From: [email protected]
[mailto:[email protected]] On Behalf Of John L.
(IRONRUBY)
Sent: Tuesday,01 July 01, 2008 00:59
To: [email protected]
Subject: [Ironruby-core] SVN r118 and RubySpec integration

I just pushed SVN r118 out which contains RubySpec integration. There
are a
few things that you’ll need to do:

  1.   (Optional) get a GitHub account (http://github.com)
    
  2.   (Optional) install GIT:
    

a. Goto the msysgit project and download the .exe based installer:
http://code.google.com/p/msysgit/

b. Make sure in the GIT setup that you click on the radio button
labeled “Run Git from the Windows Command Prompt”

c. Restart your command prompt

  1.   Navigate to my page: http://github.com/jflam to see the three 
    

GIT
projects that you’ll need to clone: ironruby-tags, mspec, and rubyspec.
mspec and rubyspec are forks of the main projects so that we can add
IronRuby specific tests and potential changes to mspec. The RubySpec
committers can pull from these repositories to incorporate our changes.
ironruby-tags is a project that contains the list of rubyspec specs that
we
currently exclude to get a clean regression baseline.

  1.   If you have GIT installed, create a directory to hold these
    

projects. I use %USERPROFILE%\dev:

a. in ~\dev\ironruby-tags run: git clone
git://github.com/jflam/ironruby-tags.git

b. in ~\dev\mspec run: git clone git://github.com/jflam/mspec.git

c. in ~\dev\rubyspec run: git clone
git://github.com/jflam/rubyspec.git

  1.   If you don't have GIT installed (and why don't you??? J) you 
    

can
download the tarball using the download button in each project.

Once you have those projects in place, you’ll need to grab r118 from
RubyForge. There’s a file in \trunk called runfirst.cmd. This will
enable
skip verification for projects signed with our public key, and it will
create a default configuration file at %USERPROFILE%.irconfig.rb.

If you followed my instructions and created
%USERPROFILE%\dev[ironruby-tags,mspec,rubyspec] you’re good to go. If
you
didn’t, you’ll need to edit the paths in .irconfig.rb

You can test your setup by running the new regression test baseline rake
task:

rake regression

This should report 0 failures and 0 errors.

This is the first test of this stuff outside of my machine, so please
kick
the tires!

Thanks,

-John

Hmm … looks like an older version made it out to r118. Let me
investigate.

Thanks,
-John

Both files are the same and my entire local folder is identical to the
SVN
output.
Pete

I just looked at the files on SVN and they’re the same as mine - I’m
attaching default.irconfig.rb and context.rb - can you diff to see if
they’re the same as what’s on your machine?

I’ve fixed the quoting problem on this end.

Thanks,
-John

Oops. Sorry my fault.
My irconfig.rb was referring to the wrong folders. (I had c: rather
than
d:).
The line 668 in context.rb
Dir["#{UserEnvironment::RUBYSPEC}/1.8/core/*"].each do |path|
was never picking up the tests.
Pete

Hi John,
It was fail to run… attached file is the fixed version.

Thank you,
-Jirapong

On Tue, Jul 1, 2008 at 11:53 PM, John L. (IRONRUBY)
[email protected]

Can you try out r119 that I just pushed out? It should have a test that
catches the wrong folder problem that you ran into.

Thanks,
-John

Doh! Thanks for the fix!

Thanks,
-John

From: [email protected]
[mailto:[email protected]] On Behalf Of Jirapong Nanta
Sent: Tuesday, July 01, 2008 10:46 AM
To: [email protected]
Subject: Re: [Ironruby-core] SVN r118 and RubySpec integration

Hi John,
It was fail to run… attached file is the fixed version.

Thank you,
-Jirapong
On Tue, Jul 1, 2008 at 11:53 PM, John L. (IRONRUBY)
<[email protected]mailto:[email protected]> wrote:
Can you try out r119 that I just pushed out? It should have a test that
catches the wrong folder problem that you ran into.

Thanks,
-John

next… run got error about

C:\OpenSource\ironRuby\trunk>c:\ruby\bin\ruby.exe
c:\Users\v-jirapn\dev\mspec\bin\mspec-ci -fm -X “c:\Users\v-jirapn\dev
\ironruby-tags” “c:\Users\v-jirapn\dev\rubyspec\1.8\core\array”
c:/Users/v-jirapn/dev/mspec/lib/mspec/utils/script.rb:35:in
expand_path': couldn't find HOME environment -- expanding
~/.mspecrc’ (ArgumentError)
from c:/Users/v-jirapn/dev/mspec/lib/mspec/utils/script.rb:35:in
load' from c:/Users/v-jirapn/dev/mspec/lib/mspec/utils/script.rb:71:in main’
from c:/Users/v-jirapn/dev/mspec/bin/mspec-ci:8

Workaround by run: SET HOME=%UserProfile%

then…
run: c:\ruby\bin\ruby.exe c:\Users\v-jirapn\dev\mspec\bin\mspec-ci -fm
-X
“c:\Users\v-jirapn\dev
\ironruby-tags”
“c:\Users\v-jirapn\dev\rubyspec\1.8\core\array\hash_spec.rb”

Finished in 0.022000 seconds

1 file, 5 examples, 17 expectations, 0 failures, 0 errors

also successful to run: rake regression

Thanks,
-Jirapong

On Wed, Jul 2, 2008 at 12:55 AM, John L. (IRONRUBY)
[email protected]