I'm about to take on a new role that will involve working with puppet, so I thought a good way to get my head around the product would be to integrate it with EFS. Puppet is written in ruby, so naturally, I started with ruby. Ruby itself is a GNU configure based installation, so it's straight forward to integrate using efsdeploy. Once that's done, then I may need to extend efsdeploy itself to understand the ruby build system, but I haven't gotten that far.
Puppet only works with ruby 1.8.2 through 1.8.7, although 1.9.2 is the latest stable release, so I took a shot at building both releases. They build fine, but both tests suites fail with a SIGILL. In the case of 1.8.7-p330, the test suite produces little to no output AT ALL: [2011-01-13 19:04:22] ./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb ./runruby.rb --extout=.ext -- "./test/runner.rb" --basedir="./test" --runner=console [2011-01-13 19:04:28] Loaded suite . [2011-01-13 19:04:28] Started [2011-01-13 19:04:56] ........................................................................................................................\ ...............................................................................................................................................\ ...................................................................................................................................make: *** [test-all] Illegal instruction 1.9.2-p136 produces the same failure: [2011-01-13 19:17:24] Started [2011-01-13 19:17:31] ........................................................................................................................\ ...............................................................................................................................................\ ...............................................................................................................................................\ ....................................................................................make: *** [yes-test-all] Illegal instruction It doesn't show it, but the miniruby command is the same. What's most annoying it that under strace, there's no SIGILL at all. First comment: I think we need a generic trac component for tracking general issues with content integration, so that we can manage these issues over time. Second comment: ruby's core test suite could learn a few things from perl. I asked on #ruby-lang, and googled, and couldn't find a way to get more verbosity out of the test suite. My non-existent skills with ruby aren't helping me decode the test suite code, either. I'm going to go ahead and install these, but this is the kind of issue that really bothers me. I do NOT like ignoring test suite failures. especially fatal one's like this. If anyone else has any experience with ruby that can shed some light on this, let me know.
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
