Btw, “igem i rails” works without any issue!
Awesome, thanks =)
From: [email protected]
[mailto:[email protected]] On Behalf Of Shri B.
Sent: Wednesday, April 15, 2009 5:00 PM
To: [email protected]
Subject: Re: [Ironruby-core] Status of rubygems unit tests
Here are the latest results:
755 tests, 2422 assertions, 8 failures, 14 errors, 4 skips
The total number of tests increased after I did “gem i builder” since
some of the tests get skipped if that gem is not present. The log is at
http://gist.github.com/92738. As you can see, the main remaining issue
is that "igem cert"http://rubygems.org/read/chapter/10#page93 does not
work as OpenSSL is not implemented. Jirapong is going to take a look at
implementing it. However, most gems are unsigned, and so this is not a
big issue. If anyone knows of important gems that are signed, let us
know.
Btw, “igem i rails” works without any issue!
Also, I am working on getting the RubyGems tests included in the repo so
that they can be run as part of continuous integration.
Thanks,
Shri
From: Shri B.
Sent: Friday, April 03, 2009 2:15 PM
To: ‘[email protected]’
Subject: RE: Status of rubygems unit tests
Here are the latest results:
728 tests, 2021 assertions, 26 failures, 35 errors, 4 skips
Latests results will be available at
http://www.ironruby.net/Documentation/How_do_I_install_additional_gems%3F.
The total number of tests increased because we moved from RubyGems
version 0.9 something to the trunk of 1.3.
Jirapong has been tagging with me to help push on this which has been
very useful.
The issues we have fixed include:
the underlying IO object
non-deterministic since the code iterates a Hash. The keys of a hash are
not required to be in any order. Jirapong is going to submit a patch to
RubyGems.
should not keep the file locked. This could fix 8 errors.
Thanks,
Shri
From: [email protected]
[mailto:[email protected]] On Behalf Of Shri B.
Sent: Monday, March 16, 2009 11:10 PM
To: ‘[email protected]’
Subject: [Ironruby-core] Status of rubygems unit tests
I have been working on making the rubygem unit tests (from
git://github.com/vvs/rubygems.git) pass with IronRuby. When I started,
the results looked like this.
707 tests, 1170 assertions, 9 failures, 352 errors, 1 skips
Half the tests (9+352/707) were failing (or half were passing depending
on how you want to look at it). The main culprits were Zlib::GzipWriter,
YAML.quick_emit and Zlib::Deflate. After fixing these issues, the
results look like this:
707 tests, 1881 assertions, 40 failures, 53 errors, 4 skips
It’s a good improvement. Errors (where the tests cannot even run
properly) account for 8% (53/707), and failures (functionality defects)
can now show through - in 5% (40/707) of the tests, for a pass rate of
87%. The errors are because of the following exceptions in descending
order of occurrence. The number at the start is the count of how often
the error happened.
9: dump format error(9)
8: ERROR: Failed to build gem native extension.
5: dump format error(8)
5: marshal data too short
4: uninitialized constant OpenSSL::X509
2: uninitialized constant OpenSSL::PKey
2: trying to seek on a non-existent stream?
2: ERROR: Failed to build gem native extension.
2: SSL is not installed on this system
2: SocketError: An established connection was aborted by the software in
your host machine
I will keep pushing on the tests. The failures will be a bit more work
to narrow down as some expectation fails, possibly much after a bug
introduced a bad result in the system. If anyone wants to help dig into
the failures, let me know, and I can help you get set up.
Thanks,
Shri