Re: public windows build server

Ruby IronRuby
1

That’s kind of odd that we have that shortname issue on a current gen
OS. I have seen issues with time being off, I just didn’t realize it was
a Redmond-centricity issue. See if MRI 1.8.6p287 or higher fixes the MRI
tests, we might be testing something that changed in 1.8.7. None of the
failures look to be region failures, although it wouldn’t surprise me to
be honest.

I wonder if running it out of hudson’s account would cover up the
shortname issue, although we do need to figure out what is going on
there. Those other changes should get more tests passing.

From: Ivan Porto C. [email protected]
Sent: October 11, 2009 3:52 PM
To: Jim D. [email protected]
Cc: [email protected] [email protected]
Subject: Re: [Ironruby-core] public windows build server

OS: Windows 2008 R2
Timezone: GMT+2
MRI: 1.8.7-p72

I can move the timezone to UTC if that would help.

There are also different regions there from the US
My region is Dutch (Belgium)

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

On Mon, Oct 12, 2009 at 12:44 AM, Jim D.
<[email protected]mailto:[email protected]> wrote:
Ivan, what OS, timezone and version of MRI are on that machine?

From: Shri B.
<[email protected]mailto:[email protected]>
Sent: October 11, 2009 1:07 PM
To: Ivan Porto C. <[email protected]mailto:[email protected]>
Cc: [email protected]mailto:[email protected]
<[email protected]mailto:[email protected]>

Subject: Re: [Ironruby-core] public windows build server

Tried it again and it works now. I took a quick look at the log at
http://ironruby.koolkraft.net/job/IronRuby/lastFailedBuild/console and
its good that most of the tests pass!

The test failures need more investigation but seem like fixable test
issues:

• RubySpec B fails because of short file name vs long file name
issue.

• ActiveSupport seems to fail because of timezone issues and the
tests might need to be disabled like a number of other tests disabled in
Merlin\Languages\Ruby\Tests\Scripts\ActiveSupportTests.rb which also
fail with MRI…

• RubySpec C has this output. Don’t remember seeing it before:

Socket::IPSocket#getaddress raises an error on unknown hostnames FAILED

Expected SocketError but no exception was raised

• No idea about the Legacy test failures. There is no output
unfortunately. We need to fix the harness.
CRubyDriver
log @
C:\Users\Administrator.hudson\jobs\IronRuby\workspace\Merlin\Main/Languages/Ruby/Tests/cruby_10060241.log
…x(test_enumerable.rb)x(test_hash.rb)…sx(test_dir.rb)…

From: Ivan Porto C.
[mailto:[email protected]mailto:[email protected]]
Sent: Saturday, October 10, 2009 1:08 AM
To: Shri B.
Subject: Re: [Ironruby-core] public windows build server

for the time being I have to use dyndns. I can get there from outside my
home but if the ip changed it takes a few minutes to be sent to
dyndns.orghttp://dyndns.org

In a few weeks I’ll have a static IP, then this shouldn’t happen
anymore.

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

On Sat, Oct 10, 2009 at 5:54 AM, Shri B.
<[email protected]mailto:[email protected]> wrote:
Just tried the url and it does not work (“The IP address for the website
you requested could not be found.”). I can see Koolkraft.net itself
though.

From:
[email protected]mailto:[email protected]
[mailto:[email protected]mailto:[email protected]]
On Behalf Of Ivan Porto C.
Sent: Friday, October 09, 2009 3:58 PM
To: ironruby-core
Subject: [Ironruby-core] public windows build server

Hi

I’ve set up a windows build server too. http://ironruby.koolkraft.net

Same goes if you want an ironruby project to be added to the build and
run after every ironruby build. Let me know and we’ll see about getting
you set up.

The ironruby build is failing because the tests are failing I’m not sure
if that is meant to be the case

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

2

I remember now discussing the short-file name issue with Ray and Kevin a
while ago. “Dir.chdir changes to the specified directory” was failing
for them as well. This is a because of a bug in IronRuby in
File.expand_path - MRI has complicated rules of when File.expand_path
uses 8.3 file names whereas IronRuby always expands the file names to
the full file name. The failure can be worked around by setting TMP to a
non-expanding path. Or we can mark those tests as unstable to disable
them.

About the Legacy tests, the output does point to a log file. Could you
search the log file for the failing test names and send the output of
those tests from the log file?

Btw, I was able to access http://ironruby.koolkraft.net/ from home, but
I am not able to do so from work. I tried “ipconfig /release & ipconfig
/renew” but that did not help. Not sure if there is any issue when
running from behind the company firewall.

From: [email protected]
[mailto:[email protected]] On Behalf Of Jim D.
Sent: Sunday, October 11, 2009 5:27 PM
To: Ivan Porto C.
Cc: [email protected]
Subject: Re: [Ironruby-core] public windows build server

That’s kind of odd that we have that shortname issue on a current gen
OS. I have seen issues with time being off, I just didn’t realize it was
a Redmond-centricity issue. See if MRI 1.8.6p287 or higher fixes the MRI
tests, we might be testing something that changed in 1.8.7. None of the
failures look to be region failures, although it wouldn’t surprise me to
be honest.

I wonder if running it out of hudson’s account would cover up the
shortname issue, although we do need to figure out what is going on
there. Those other changes should get more tests passing.

From: Ivan Porto C. [email protected]
Sent: October 11, 2009 3:52 PM
To: Jim D. [email protected]
Cc: [email protected] [email protected]
Subject: Re: [Ironruby-core] public windows build server
OS: Windows 2008 R2
Timezone: GMT+2
MRI: 1.8.7-p72
I can move the timezone to UTC if that would help.

There are also different regions there from the US
My region is Dutch (Belgium)

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

On Mon, Oct 12, 2009 at 12:44 AM, Jim D.
<[email protected]mailto:[email protected]> wrote:
Ivan, what OS, timezone and version of MRI are on that machine?

From: Shri B.
<[email protected]mailto:[email protected]>
Sent: October 11, 2009 1:07 PM
To: Ivan Porto C. <[email protected]mailto:[email protected]>
Cc: [email protected]mailto:[email protected]
<[email protected]mailto:[email protected]>

Subject: Re: [Ironruby-core] public windows build server
Tried it again and it works now. I took a quick look at the log at
http://ironruby.koolkraft.net/job/IronRuby/lastFailedBuild/console and
its good that most of the tests pass!

The test failures need more investigation but seem like fixable test
issues:

  •     RubySpec B fails because of short file name vs long file name

issue.

  •     ActiveSupport seems to fail because of timezone issues and the

tests might need to be disabled like a number of other tests disabled in
Merlin\Languages\Ruby\Tests\Scripts\ActiveSupportTests.rb which also
fail with MRI…

  •     RubySpec C has this output. Don't remember seeing it before:

Socket::IPSocket#getaddress raises an error on unknown hostnames FAILED

Expected SocketError but no exception was raised

  •     No idea about the Legacy test failures. There is no output

unfortunately. We need to fix the harness.
CRubyDriver
log @
C:\Users\Administrator.hudson\jobs\IronRuby\workspace\Merlin\Main/Languages/Ruby/Tests/cruby_10060241.log
…x(test_enumerable.rb)x(test_hash.rb)…sx(test_dir.rb)…

From: Ivan Porto C.
[mailto:[email protected]mailto:[email protected]]
Sent: Saturday, October 10, 2009 1:08 AM
To: Shri B.
Subject: Re: [Ironruby-core] public windows build server

for the time being I have to use dyndns. I can get there from outside my
home but if the ip changed it takes a few minutes to be sent to
dyndns.orghttp://dyndns.org

In a few weeks I’ll have a static IP, then this shouldn’t happen
anymore.

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

On Sat, Oct 10, 2009 at 5:54 AM, Shri B.
<[email protected]mailto:[email protected]> wrote:
Just tried the url and it does not work (“The IP address for the website
you requested could not be found.”). I can see Koolkraft.net itself
though.

From:
[email protected]mailto:[email protected]
[mailto:[email protected]mailto:[email protected]]
On Behalf Of Ivan Porto C.
Sent: Friday, October 09, 2009 3:58 PM
To: ironruby-core
Subject: [Ironruby-core] public windows build server

Hi

I’ve set up a windows build server too. http://ironruby.koolkraft.net

Same goes if you want an ironruby project to be added to the build and
run after every ironruby build. Let me know and we’ll see about getting
you set up.

The ironruby build is failing because the tests are failing I’m not sure
if that is meant to be the case

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto C.
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)