Problem installing testunit 0.1.4 on OSX

ruby-talk
1

Hi

I am trying to install testunit-0.1.4 on OSX but I get the following
problem.

%ruby setup.rb install
setup.rb: entering install phase…
—> packages
—> packages/runit-compat
—> lib
mkdir -p /usr/lib/ruby/site_ruby/1.6/
install rubyunit.rb /usr/lib/ruby/site_ruby/1.6/
—> lib/runit
mkdir -p /usr/lib/ruby/site_ruby/1.6/runit
install assert.rb /usr/lib/ruby/site_ruby/1.6/runit
install error.rb /usr/lib/ruby/site_ruby/1.6/runit
install testcase.rb /usr/lib/ruby/site_ruby/1.6/runit
install testresult.rb /usr/lib/ruby/site_ruby/1.6/runit
install testsuite.rb /usr/lib/ruby/site_ruby/1.6/runit
install testunit-installed /usr/lib/ruby/site_ruby/1.6/runit
install topublic.rb /usr/lib/ruby/site_ruby/1.6/runit
—> lib/runit/cui
mkdir -p /usr/lib/ruby/site_ruby/1.6/runit/cui
install testrunner.rb /usr/lib/ruby/site_ruby/1.6/runit/cui
<— lib/runit/cui
<— lib/runit
<— lib
<— packages/runit-compat
—> packages/testunit
—> lib
Loaded suite TS_TestUnit
Started…
…install failed
hook /testunit-0.1.4/packages/testunit/lib/pre-install.rb failed:
stack level too deep
try ‘ruby setup.rb --help’ for usage

It appears to install runit but is not able to install testunit.

My Ruby version is 1.6.7 - Can anyone help me?

Cheers

Ross

2

hook /testunit-0.1.4/packages/testunit/lib/pre-install.rb failed:
stack level too deep

Verify the value of stacksize with `ulimit -a', and change it if it's too
low

Guy Decoux

3

In article 200211201720.gAKHKSf08215@moulon.inra.fr,

···

ts decoux@moulon.inra.fr wrote:

hook /testunit-0.1.4/packages/testunit/lib/pre-install.rb failed:
stack level too deep

Verify the value of stacksize with `ulimit -a’, and change it if it’s too
low

Unfortunately this command was not found.

% ulimit -a
ulimit: Command not found.

I am running OSX 10.2.2

Ross

4

On OS X that’s more likely ‘limit stacksize’. :slight_smile:

···

On Wednesday, November 20, 2002, at 10:22 AM, ts wrote:

hook /testunit-0.1.4/packages/testunit/lib/pre-install.rb failed:
stack level too deep

Verify the value of stacksize with `ulimit -a’, and change it if it’s
too
low

No mistake is more common and more fatuous than appealing to logic in
cases which are beyond her jurisdiction.
-Samuel Butler, writer (1835-1902)

5

Unfortunately this command was not found.

% ulimit -a
ulimit: Command not found.

I am running OSX 10.2.2

If you’re running tcsh, use
% limit stacksize

<not_so_relevant_chatter>

Or
% limit -h stacksize
To to see the current hard stacksize limit
% unlimit stacksize
To set the stacksize limit to the current hard stacksize limit

You can find more info about tcsh builtins here:
% man tcsh

</not_so_relevant_chatter>

Hannes

···

–
Mit freundlichen Grüssen / best regards

Hannes Wyss
Konzeption & Entwicklung

+41 1 350 85 85

www.ywesee.com > intellectual capital connected > generika.cc

6

That’s because in tcsh it’s ‘limit stacksize’. I’d suggest you use the
man searching facility in PB to look this up because the results of man
limit are just too unwieldy for the terminal.

···

On Wednesday, November 20, 2002, at 01:33 PM, Ross Shaw wrote:

In article 200211201720.gAKHKSf08215@moulon.inra.fr,
ts decoux@moulon.inra.fr wrote:

hook /testunit-0.1.4/packages/testunit/lib/pre-install.rb failed:
stack level too deep

Verify the value of stacksize with `ulimit -a’, and change it if
it’s too
low

Unfortunately this command was not found.

% ulimit -a
ulimit: Command not found.

I am running OSX 10.2.2

No mistake is more common and more fatuous than appealing to logic in
cases which are beyond her jurisdiction.
-Samuel Butler, writer (1835-1902)

7

In article BA024DDC.CE9A%hwyss@ywesee.com,

···

Hannes Wyss hwyss@ywesee.com wrote:

Unfortunately this command was not found.

% ulimit -a
ulimit: Command not found.

I am running OSX 10.2.2

If you’re running tcsh, use
% limit stacksize

<not_so_relevant_chatter>

Or
% limit -h stacksize
To to see the current hard stacksize limit
% unlimit stacksize
To set the stacksize limit to the current hard stacksize limit

You can find more info about tcsh builtins here:
% man tcsh

</not_so_relevant_chatter>

Hannes

Thanks very much - this worked

Ross