First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 116875
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Ruby Team <ruby@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Caleb Tennis <caleb@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 116875 depends on: Show dependency tree
Bug 116875 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-12-27 06:38 0000
See summary.

------- Comment #1 From AJ Armstrong 2005-12-27 18:07:22 0000 -------
Began testing for amd64.  Ran the rake test suite included in the tarball from
the website.  Functional tests (rake tf) would not run due to an apparent bad
path (./bin/rake).  Contrib test (rake tc) passes.  Unit tests (rake tu) had
113 passed tests, 3 failed tests (details below).  Could someone knowledgeable
about the package determine if those tests can be ignored for stability? 
Emerge info follows test output:
############################################################################
oberon rake # rake tf
(in /root/work/rake)
./Rakefile:247: warning: ambiguous first argument; put parentheses or even
spaces
./Rakefile:252: warning: ambiguous first argument; put parentheses or even
spaces
ruby: No such file or directory -- ./bin/rake (LoadError)
UNABLE TO RUN FUNCTIONAL TESTS
No Session Found
############################################################################
oberon rake # rake tc
(in /root/work/rake)
./Rakefile:247: warning: ambiguous first argument; put parentheses or even
spaces
./Rakefile:252: warning: ambiguous first argument; put parentheses or even
spaces
ruby: No such file or directory -- ./bin/rake (LoadError)
Loaded suite /usr/lib64/ruby/site_ruby/1.8/rake/rake_test_loader
Started
.
Finished in 0.000443 seconds.

1 tests, 6 assertions, 0 failures, 0 errors
############################################################################
oberon rake # rake tu
(in /root/work/rake)
./Rakefile:247: warning: ambiguous first argument; put parentheses or even
spaces
./Rakefile:252: warning: ambiguous first argument; put parentheses or even
spaces
ruby: No such file or directory -- ./bin/rake (LoadError)
Loaded suite /usr/lib64/ruby/site_ruby/1.8/rake/rake_test_loader
Started
..................................................................................F..........................F....F.
Finished in 9.497422 seconds.

  1) Failure:
test_create(TestPackageTask) [./test/test_package_task.rb:29]:
<false> is not true.

  2) Failure:
test_both_pattern_and_test_files(TestTestTask) [./test/test_test_task.rb:73]:
<["a.rb", "b.rb", "install.rb"]> expected but was
<["a.rb", "b.rb"]>.

  3) Failure:
test_pattern(TestTestTask) [./test/test_test_task.rb:50]:
<["install.rb"]> expected but was
<[]>.

116 tests, 375 assertions, 3 failures, 0 errors
rake aborted!
Command failed with status (1): [/usr/bin/ruby18 -w -Ilib "/usr/lib64/ruby/...]


############################################################################

Portage 2.0.53 (default-linux/amd64/2005.1, gcc-4.0.2, glibc-2.3.6-r1,
2.6.14-gentoo-r5 x86_64)
=================================================================
System uname: 2.6.14-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks maketest multilib-strict sandbox sfperms strict
test"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/etc/portage/overlay"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 alsa avi berkdb bitmap-fonts bzip2 crypt cups eds emboss encode
expat foomaticdb fortran gdbm gif gmp gpm gstreamer gtk2 imlib ipv6 java jpeg
ldap lzw lzw-tiff mp3 mpeg mysql ncurses nls opengl pam pdflib perl png python
quicktime readline ruby sdl spell ssl tcpd tiff truetype-fonts type1-fonts udev
usb userlocales xpm xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS

------- Comment #2 From Caleb Tennis 2006-01-12 05:17:51 0000 -------
The first failure on SESSION is okay - we don't have a session gem in portage
so it's no big deal.

The other two (tc and tu) both pass for me.  Did you already have rake built
when you ran them (it's looking for it in the ./bin directory).  I ran them on
my portage tmpdir after it had already built and installed...

------- Comment #3 From Simon Stelling (RETIRED) 2006-01-15 04:52:12 0000 -------
i've got some problems too. i just emerged it with FEATURES=test and it seems
to hang here:

>>> Test phase [check]: dev-lang/ruby-1.8.3
test succeeded
./miniruby ./runruby.rb --extout=.ext -- -C "./test" runner.rb --runner=console
Loaded suite .
Started
..............................................F

at least there wasn't any progress for >15 minutes

------- Comment #4 From Simon Stelling (RETIRED) 2006-01-27 04:10:06 0000 -------
ruby, could you please tell me whether the problem in comment #3 is save to
ignore or not? is it amd64-specific after all?

------- Comment #5 From Caleb Tennis 2006-02-09 06:03:06 0000 -------
I can't recreate #3 on x86, so I'm not sure.  I don't know why it wouldn't be
safe, but it's interesting.

------- Comment #6 From Markus Rothe 2006-02-17 14:08:04 0000 -------
Hi,

I would need to mark rubygems-0.8.11-r* stable on ppc64, as <=rubygems-0.8.11
was never marked ~ppc64. Please give advise if I should mark rubygems-0.8.11
~ppc64 (wait another 30 days) or if it is save to mark -r1, -r2 or -r3 stable.

Please note that >=ruby-config-0.3.2 would need to go stable, too.

Regards,

Markus

------- Comment #7 From Caleb Tennis 2006-02-22 11:02:07 0000 -------
I just committed rubygems 0.8.11-r4, which is the only one I would recommend
marking stable in the near future (the previous three didn't work like I had
intended).  Still, I'd wait a little bit before marking.

------- Comment #8 From Markus Rothe 2006-03-19 08:15:12 0000 -------
stable on ppc64

------- Comment #9 From Simon Stelling (RETIRED) 2006-04-30 02:24:36 0000 -------
 _  _ _  _| /|_|   __|_ _ |_ | _
(_|| | |(_|(_) |  _\ | (_||_)|(/_

First Last Prev Next    No search results available      Search page      Enter new bug