# Rbtree tests fail on 1.8.2, but not on 1.8.4 **URL:** \ **Category:** Ruby\ **Created:** [March 8, 2006, 8:00pm UTC](https://www.ruby-forum.com/t/rbtree-tests-fail-on-1-8-2-but-not-on-1-8-4/78634 "2006-03-08T20:00:06Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\ **Post date:** [March 8, 2006, 8:00pm UTC](https://www.ruby-forum.com/t/rbtree-tests-fail-on-1-8-2-but-not-on-1-8-4/78634/1 "2006-03-08T20:00:06Z")
Hi all, I dug up the rbtree 0.1.3 tarball from the RAA cache and am trying to build it. It builds fine, but the tests fail. Unfortunately for me, this test is indicative of the exact functionality I require. What’s wierd is that the test fails on ruby 1.8.2, but it passes on ruby 1.8.4. Does anyone have any ideas about why this would occur and what I can do about it (other than just moving up to 1.8.4…) ? Output from attempt with 1.8.2: rodimus:~/ruby-rbtree\> ruby extconf.rb checking for allocation framework... yes checking for rb\_obj\_init\_copy()... yes checking for rb\_block\_proc()... yes checking for rb\_yield\_values()... yes checking for rb\_marshal\_dump()... yes checking for rb\_marshal\_load()... yes checking for inline keyword... \_\_inline creating Makefile rodimus:~/ruby-rbtree\> make gcc -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -fPIC -std=c89 -pedantic -Wall -Wno-long-long -I. -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I. -DNDEBUG -DHAVE\_OBJECT\_ALLOCATE -DHAVE\_RB\_OBJ\_INIT\_COPY -DHAVE\_RB\_BLOCK\_PROC -DHAVE\_RB\_YIELD\_VALUES -DHAVE\_RB\_MARSHAL\_DUMP -DHAVE\_RB\_MARSHAL\_LOAD -Dinline=\_\_inline -c dict.c gcc -fPIC -O2 -g -pipe -march=i386 -mcpu=i686 -fPIC -std=c89 -pedantic -Wall -Wno-long-long -I. -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux -I. -DNDEBUG -DHAVE\_OBJECT\_ALLOCATE -DHAVE\_RB\_OBJ\_INIT\_COPY -DHAVE\_RB\_BLOCK\_PROC -DHAVE\_RB\_YIELD\_VALUES -DHAVE\_RB\_MARSHAL\_DUMP -DHAVE\_RB\_MARSHAL\_LOAD -Dinline=\_\_inline -c rbtree.c gcc -shared -L'/usr/lib' -Wl,-R'/usr/lib' -o rbtree.so dict.o rbtree.o -Wl,-R -Wl,/usr/lib -L/usr/lib -L. -lruby -ldl -lcrypt -lm -lc rodimus:~/ruby-rbtree\> ruby test.rb Loaded suite test Started ....................................................test.rb:201: warning: block supersedes default value argument ...............F................ Finished in 0.02627 seconds. 1. Failure: test\_readjust(RBTreeTest) [test.rb:592]: exception expected but was Class: Message: \<"undefined method `>' for false:FalseClass"> ---Backtrace--- test.rb:592:in`readjust’ test.rb:592:in `test_readjust' test.rb:592:in`assert\_raise’ test.rb:592:in `test\_readjust’ * * * 84 tests, 278 assertions, 1 failures, 0 errors rodimus:~/ruby-rbtree\> ruby --version ruby 1.8.2 (2004-12-25) [i386-linux] rodimus:~/ruby-rbtree\> Here’s the output from the same process on Ruby 1.8.4 (extconf and make output removed for brevity): puma:~/rbtree-0.1.3\> ruby test.rb Loaded suite test Started ....................................................test.rb:201: warning: block supersedes default value argument ...............test.rb:609: warning: RBTree#readjust() uses current comparison block, use RBTree#readjust(nil) to set default comparison block ................. Finished in 0.134389 seconds. 84 tests, 287 assertions, 0 failures, 0 errors puma:~/rbtree-0.1.3\> ruby --version ruby 1.8.4 (2005-12-24) [i686-linux] puma:~/rbtree-0.1.3\> – Toby DiPasquale ---
**Author:** ![casper\_the\_ghost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/58956e/32.png) [@casper\_the\_ghost](https://www.ruby-forum.com/u/casper_the_ghost)\ **Post date:** [March 8, 2006, 8:10pm UTC](https://www.ruby-forum.com/t/rbtree-tests-fail-on-1-8-2-but-not-on-1-8-4/78634/2 "2006-03-08T20:10:30Z")
On Thu, 9 Mar 2006, Toby DiPasquale wrote: > Hi all, > > I dug up the rbtree 0.1.3 tarball from the RAA cache and am trying to > build it. It builds fine, but the tests fail. Unfortunately for me, this > test is indicative of the exact functionality I require. > > What’s wierd is that the test fails on ruby 1.8.2, but it passes on ruby > 1.8.4. Does anyone have any ideas about why this would occur and what I > can do about it (other than just moving up to 1.8.4…) ? i can confirm the above at least… may have time later to look into it. more later… -a