Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote: I took a look at this a few weeks ago. The problem is the code in the cont.c file which implements continuations. A thread saves its own stack and its thread context itself while it is running. The ruby programmers believe that that the saved info can be used by another thread to switch over. They are wrong! This is simply ill-formed code; wrong usage of the makecontext()/swapcontext() functions. It is a miracle that it works on other architectures - on sparc it did after doing some dirty tricks. The problem causes crashes which are almost impossible to understand with the debugger. The code was written in 2007 and made a lot of trouble until now; when you take a look to cont.c, you are see some really weird code fragments - dirty hacks to workaround some fundamental design flaws. I'm not satisfied with the code quality of the ruby project at all; I don't understand how it could be included in a ruby version that is for production use. So the continuations and perhaps some related threading features are broken - very advanced and new features in Ruby. I think a fix is feasable for platforms which use makecontext()/swapcontext() - as Linux is (rather than Windows Win32 functions). What can be implememnted is that a thread switches to another context/stack; the initial context/stack is saved after that. The thread switches back to the initial context/stack finally. This means: - The performance becomes worse due to additional context switches. I think it isn't that bad; the ruby code copies over huge portions of memory in its implementation all the time; the entire original code is a huge performance penalty (if it wouldn't crash). I don't believe that the additional context switches makes it noticeable worse. - The patch would be a real patch bomb. It would remove a lot of mess for (not working) ia64 workarounds and the most recent sparc patches of Debian as well. The patch replaces a lot of code of cont.c. - The patch would change the implementation for all Debian archs, not only ia64. I appreciate comments on that. Sounds good to me. It will be awesome if you could do that! :-) I would say let's get that patch written, test it, make sure it doesn't break anything, and them we can talk to upstream. I am not comfortable with carrying such a huge patch on the Debian package, since I do not have much experience of such low-level stuff. For now I'd prefer the 'wheezy-ignore' rather than removing the ia64 ruby package. Looks like this should be the way to go. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Control: tag 653582 wheezy-ignore Control: tag 593141 wheezy-ignore On Sat, Dec 8, 2012 at 11:11:56 -0300, Antonio Terceiro wrote: On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote: For now I'd prefer the 'wheezy-ignore' rather than removing the ia64 ruby package. Looks like this should be the way to go. Agreed. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Processing control commands: tag 653582 wheezy-ignore Bug #653582 [ruby1.9.1] Segfaults when running ruby-hpricot's test suite on ia64 Added tag(s) wheezy-ignore. tag 593141 wheezy-ignore Bug #593141 [src:ruby1.9.1] ruby1.9.1: FTBFS on ia64: test suite segfaults Added tag(s) wheezy-ignore. -- 593141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593141 653582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Processing control commands: tag 653582 wheezy-ignore Bug #653582 [ruby1.9.1] Segfaults when running ruby-hpricot's test suite on ia64 Ignoring request to alter tags of bug #653582 to the same tags previously set tag 593141 wheezy-ignore Bug #593141 [src:ruby1.9.1] ruby1.9.1: FTBFS on ia64: test suite segfaults Ignoring request to alter tags of bug #593141 to the same tags previously set -- 593141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593141 653582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
I took a look at this a few weeks ago. The problem is the code in the cont.c file which implements continuations. A thread saves its own stack and its thread context itself while it is running. The ruby programmers believe that that the saved info can be used by another thread to switch over. They are wrong! This is simply ill-formed code; wrong usage of the makecontext()/swapcontext() functions. It is a miracle that it works on other architectures - on sparc it did after doing some dirty tricks. The problem causes crashes which are almost impossible to understand with the debugger. The code was written in 2007 and made a lot of trouble until now; when you take a look to cont.c, you are see some really weird code fragments - dirty hacks to workaround some fundamental design flaws. I'm not satisfied with the code quality of the ruby project at all; I don't understand how it could be included in a ruby version that is for production use. So the continuations and perhaps some related threading features are broken - very advanced and new features in Ruby. I think a fix is feasable for platforms which use makecontext()/swapcontext() - as Linux is (rather than Windows Win32 functions). What can be implememnted is that a thread switches to another context/stack; the initial context/stack is saved after that. The thread switches back to the initial context/stack finally. This means: - The performance becomes worse due to additional context switches. I think it isn't that bad; the ruby code copies over huge portions of memory in its implementation all the time; the entire original code is a huge performance penalty (if it wouldn't crash). I don't believe that the additional context switches makes it noticeable worse. - The patch would be a real patch bomb. It would remove a lot of mess for (not working) ia64 workarounds and the most recent sparc patches of Debian as well. The patch replaces a lot of code of cont.c. - The patch would change the implementation for all Debian archs, not only ia64. I appreciate comments on that. For now I'd prefer the 'wheezy-ignore' rather than removing the ia64 ruby package. Stephan If you want to read something pleasing about ia64 for a change, you can take a look at bug#659186 or #582774. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Mon, 16 Jan 2012 21:20:07 +0100 Lucas Nussbaum lu...@debian.org wrote: Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. To recap: ruby1.9.1 on ia64 is broken, neglected and lucas as one of its maintainers agrees to remove it on ia64. Dear release team: How do we move this forward? Should I follow http://wiki.debian.org/ftpmaster_Removals? -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Thu, Dec 6, 2012 at 10:22:00 +0100, Michael Stapelberg wrote: On Mon, 16 Jan 2012 21:20:07 +0100 Lucas Nussbaum lu...@debian.org wrote: Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. To recap: ruby1.9.1 on ia64 is broken, neglected and lucas as one of its maintainers agrees to remove it on ia64. Dear release team: How do we move this forward? Should I follow http://wiki.debian.org/ftpmaster_Removals? Start by making a list of affected packages. Then figure out which one would need complete removal and which ones need source changes to disable the ruby parts on ia64. Then run away screaming. Cheers, Julien signature.asc Description: Digital signature
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Michael Stapelberg dijo [Thu, Dec 06, 2012 at 10:22:00AM +0100]: On Mon, 16 Jan 2012 21:20:07 +0100 Lucas Nussbaum lu...@debian.org wrote: Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. To recap: ruby1.9.1 on ia64 is broken, neglected and lucas as one of its maintainers agrees to remove it on ia64. Dear release team: How do we move this forward? Should I follow http://wiki.debian.org/ftpmaster_Removals? Wow... I have never had access to a IA64 machine. And yes, we are aware of this breakage for a long time. But... How many packages in the archive depend on the default version of Ruby? We can argue that most Ruby packages are likely to be still usable under Ruby 1.8. Sigh... I don't like the idea of dropping Ruby1.9.1 altogether from an architecture, but in this light, I cannot provide any alternatives. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
What is broken about it? Has anyone estimated how much effort it would take to fix? Are we talking needing assembly language bindings or just some dumb SIGBUS error? Patrick Baggett On Thu, Dec 6, 2012 at 11:37 AM, Gunnar Wolf gw...@gwolf.org wrote: Michael Stapelberg dijo [Thu, Dec 06, 2012 at 10:22:00AM +0100]: On Mon, 16 Jan 2012 21:20:07 +0100 Lucas Nussbaum lu...@debian.org wrote: Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. To recap: ruby1.9.1 on ia64 is broken, neglected and lucas as one of its maintainers agrees to remove it on ia64. Dear release team: How do we move this forward? Should I follow http://wiki.debian.org/ftpmaster_Removals? Wow... I have never had access to a IA64 machine. And yes, we are aware of this breakage for a long time. But... How many packages in the archive depend on the default version of Ruby? We can argue that most Ruby packages are likely to be still usable under Ruby 1.8. Sigh... I don't like the idea of dropping Ruby1.9.1 altogether from an architecture, but in this light, I cannot provide any alternatives. -- To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121206173741.gc28...@gwolf.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Thu, Dec 06, 2012 at 06:13:31PM +0100, Julien Cristau wrote: On Thu, Dec 6, 2012 at 10:22:00 +0100, Michael Stapelberg wrote: On Mon, 16 Jan 2012 21:20:07 +0100 Lucas Nussbaum lu...@debian.org wrote: Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. To recap: ruby1.9.1 on ia64 is broken, neglected and lucas as one of its maintainers agrees to remove it on ia64. Dear release team: How do we move this forward? Should I follow http://wiki.debian.org/ftpmaster_Removals? Start by making a list of affected packages. Then figure out which one would need complete removal and which ones need source changes to disable the ruby parts on ia64. Then run away screaming. Revisiting your previous suggestion about this ... Removal would be second best after making it work, IMO. If we know it doesn't work at all then there's no point shipping it. If it kinda sorta works but not completely, wheezy-ignore might make more sense. I would say it does kinda sorta works but not completely ... so maybe wheezy-ignore should be the case. Yes, it segfaults when building a single package on ia64, and will probably segfault in a specific point when running its own test suite¹, but apart from that, we don't have evidence suggesting that ruby1.9.1 is completely broken on ia64. ¹ test suite which is known to exercise the code in interesting and not always realistic ways. It would be nice to read reports from people actually using ruby1.9.1 on ia64, though. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Mon, Sep 03, 2012 at 09:51:28PM +0200, Lucas Nussbaum wrote: On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote: ruby1.9.1 is known to be broken on ia64 (see #593141). It currently builds only because the test suite is disabled on that architecture, but the fact that other Ruby packages fail to build on ia64 doesn't surprise me. Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. Dear RT, If you prefer the option of shipping a known-broken ruby1.9.3 (on ia64), maybe it would be better to tag this bug wheezy-ignore now? Given that ia64 will be no longer be a release arch after Wheezy and that this problem is even present in Squeeze, this seems sensible? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On Mon, Sep 3, 2012 at 21:51:28 +0200, Lucas Nussbaum wrote: On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote: ruby1.9.1 is known to be broken on ia64 (see #593141). It currently builds only because the test suite is disabled on that architecture, but the fact that other Ruby packages fail to build on ia64 doesn't surprise me. Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. Dear RT, If you prefer the option of shipping a known-broken ruby1.9.3 (on ia64), maybe it would be better to tag this bug wheezy-ignore now? Removal would be second best after making it work, IMO. If we know it doesn't work at all then there's no point shipping it. If it kinda sorta works but not completely, wheezy-ignore might make more sense. Cheers, Julien signature.asc Description: Digital signature
Bug#593141: Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote: ruby1.9.1 is known to be broken on ia64 (see #593141). It currently builds only because the test suite is disabled on that architecture, but the fact that other Ruby packages fail to build on ia64 doesn't surprise me. Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. Dear RT, If you prefer the option of shipping a known-broken ruby1.9.3 (on ia64), maybe it would be better to tag this bug wheezy-ignore now? Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
reassign 653582 ruby1.9.1 retitle 653582 Segfaults when running ruby-hpricot's test suite thanks Hi, I do not have access to IA64 hardware, but this smells much like a bug in Ruby itself, in which ruby-hpricot's tests trip. I think the proper course is to report this to the upstream bugtracker, but they request the verbose output from the interpreter. I don't have a proper build environment so I can try this. Please try: - Build the package until the point it breaks at - Run the test that failed manually: $ ruby1.9.1 -v -I test/ -I debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/ test/test_preserved.rb Ruby1.9.1 maintainers: Can I entrust you the assessing and forwarding of this bug (as you will surely be better fitted to judge it than me)? Just FWIW, here is the output on my system (AMD64): $ ruby1.9.1 -v -I test/ -I debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/ test/test_preserved.rb ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:230: warning: assigned but unused variable - i /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:298: warning: (...) interpreted as grouped expression /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:297: warning: assigned but unused variable - oop /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:615: warning: assigned but unused variable - links /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/elements.rb:490: warning: assigned but unused variable - idx /tmp/ruby-hpricot-0.8.5/test/load_files.rb:2: warning: setting Encoding.default_external Loaded suite test/test_preserved Started .. Finished in 0.406052506 seconds. 6 tests, 5950 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed 14.78 tests/s, 14653.28 assertions/s -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
(Adding -ia64 to Cc) On 15/01/12 at 12:42 -0600, Gunnar Wolf wrote: reassign 653582 ruby1.9.1 retitle 653582 Segfaults when running ruby-hpricot's test suite thanks Hi, I do not have access to IA64 hardware, but this smells much like a bug in Ruby itself, in which ruby-hpricot's tests trip. I think the proper course is to report this to the upstream bugtracker, but they request the verbose output from the interpreter. I don't have a proper build environment so I can try this. Please try: - Build the package until the point it breaks at - Run the test that failed manually: $ ruby1.9.1 -v -I test/ -I debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/ test/test_preserved.rb Ruby1.9.1 maintainers: Can I entrust you the assessing and forwarding of this bug (as you will surely be better fitted to judge it than me)? Just FWIW, here is the output on my system (AMD64): $ ruby1.9.1 -v -I test/ -I debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/ test/test_preserved.rb ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:230: warning: assigned but unused variable - i /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:298: warning: (...) interpreted as grouped expression /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:297: warning: assigned but unused variable - oop /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/traverse.rb:615: warning: assigned but unused variable - links /tmp/ruby-hpricot-0.8.5/debian/ruby-hpricot/usr/lib/ruby/vendor_ruby/hpricot/elements.rb:490: warning: assigned but unused variable - idx /tmp/ruby-hpricot-0.8.5/test/load_files.rb:2: warning: setting Encoding.default_external Loaded suite test/test_preserved Started .. Finished in 0.406052506 seconds. 6 tests, 5950 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 100% passed 14.78 tests/s, 14653.28 assertions/s ruby1.9.1 is known to be broken on ia64 (see #593141). It currently builds only because the test suite is disabled on that architecture, but the fact that other Ruby packages fail to build on ia64 doesn't surprise me. Dear release team, at some point before the wheezy release, we need to decide what to do with Ruby 1.9.X on ia64. It has been broken for months, and hasn't seen any activity in Debian (#539141) or upstream (http://bugs.ruby-lang.org/issues/5246). I think that removing it (with all its rev-depends) makes more sense than shipping a known-broken Ruby. Lucas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653582: ruby-hpricot: FTBFS on ia64: ruby crashes while running tests
Source: ruby-hpricot Version: 0.8.5-1 Severity: serious Justification: fails to build from source User: debian-i...@lists.debian.org Usertags: ia64 ruby-hpricot FTBFS on ia64: | /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb | Loaded suite debian/ruby-tests | Started | .. | Finished in 2.919629 seconds. | | 82 tests, 6180 assertions, 0 failures, 0 errors | /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb | Run options: | | # Running tests: | | /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:25: [BUG] Segmentation fault | ruby 1.9.3p0 (2011-10-30 revision 33570) [ia64-linux] | | -- Control frame information --- | c:0030 p: s:0111 b:0111 l:0019e0 d:0019e0 CFUNC :next | c:0029 p: s:0109 b:0109 l:000102 d:000108 IFUNC | c:0028 p: s:0107 b:0107 l:000106 d:000106 CFUNC :lines | c:0027 p: s:0105 b:0105 l:000104 d:000104 CFUNC :each | c:0026 p: s:0103 b:0103 l:000102 d:000102 CFUNC :zip | c:0025 p:0095 s:0099 b:0099 l:98 d:98 METHOD /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:25 | c:0024 p:0020 s:0093 b:0093 l:92 d:92 METHOD /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:60 | c:0023 p:0073 s:0090 b:0090 l:89 d:89 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:949 | c:0022 p:0025 s:0084 b:0084 l:83 d:83 METHOD /usr/lib/ruby/1.9.1/test/unit/testcase.rb:17 | c:0021 p:0090 s:0080 b:0080 l:68 d:79 BLOCK /usr/lib/ruby/1.9.1/minitest/unit.rb:787 | c:0020 p: s:0074 b:0074 l:73 d:73 FINISH | c:0019 p: s:0072 b:0072 l:71 d:71 CFUNC :map | c:0018 p:0124 s:0069 b:0069 l:68 d:68 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:780 | c:0017 p:0020 s:0061 b:0060 l:50 d:59 BLOCK /usr/lib/ruby/1.9.1/test/unit.rb:565 | c:0016 p: s:0056 b:0056 l:55 d:55 FINISH | c:0015 p: s:0054 b:0054 l:53 d:53 CFUNC :each | c:0014 p:0053 s:0051 b:0051 l:50 d:50 METHOD /usr/lib/ruby/1.9.1/test/unit.rb:563 | c:0013 p:0189 s:0045 b:0045 l:44 d:44 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:746 | c:0012 p:0013 s:0035 b:0035 l:34 d:34 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:909 | c:0011 p:0012 s:0032 b:0032 l:23 d:31 BLOCK /usr/lib/ruby/1.9.1/minitest/unit.rb:896 | c:0010 p: s:0029 b:0029 l:28 d:28 FINISH | c:0009 p: s:0027 b:0027 l:26 d:26 CFUNC :each | c:0008 p:0068 s:0024 b:0024 l:23 d:23 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:895 | c:0007 p:0029 s:0020 b:0020 l:19 d:19 METHOD /usr/lib/ruby/1.9.1/minitest/unit.rb:884 | c:0006 p:0022 s:0016 b:0016 l:15 d:15 METHOD /usr/lib/ruby/1.9.1/test/unit.rb:21 | c:0005 p:0033 s:0012 b:0011 l:002608 d:10 BLOCK /usr/lib/ruby/1.9.1/test/unit.rb:326 | c:0004 p:0036 s:0009 b:0009 l:08 d:08 METHOD /usr/lib/ruby/1.9.1/test/unit.rb:27 | c:0003 p:0026 s:0006 b:0006 l:002608 d:05 BLOCK /usr/lib/ruby/1.9.1/test/unit.rb:325 | c:0002 p: s:0004 b:0004 l:03 d:03 FINISH | c:0001 p: s:0002 b:0002 l:0009f8 d:0009f8 TOP | | -- Ruby level backtrace information | /usr/lib/ruby/1.9.1/test/unit.rb:325:in `block in autorun' | /usr/lib/ruby/1.9.1/test/unit.rb:27:in `run_once' | /usr/lib/ruby/1.9.1/test/unit.rb:326:in `block (2 levels) in autorun' | /usr/lib/ruby/1.9.1/test/unit.rb:21:in `run' | /usr/lib/ruby/1.9.1/minitest/unit.rb:884:in `run' | /usr/lib/ruby/1.9.1/minitest/unit.rb:895:in `_run' | /usr/lib/ruby/1.9.1/minitest/unit.rb:895:in `each' | /usr/lib/ruby/1.9.1/minitest/unit.rb:896:in `block in _run' | /usr/lib/ruby/1.9.1/minitest/unit.rb:909:in `run_tests' | /usr/lib/ruby/1.9.1/minitest/unit.rb:746:in `_run_anything' | /usr/lib/ruby/1.9.1/test/unit.rb:563:in `_run_suites' | /usr/lib/ruby/1.9.1/test/unit.rb:563:in `each' | /usr/lib/ruby/1.9.1/test/unit.rb:565:in `block in _run_suites' | /usr/lib/ruby/1.9.1/minitest/unit.rb:780:in `_run_suite' | /usr/lib/ruby/1.9.1/minitest/unit.rb:780:in `map' | /usr/lib/ruby/1.9.1/minitest/unit.rb:787:in `block in _run_suite' | /usr/lib/ruby/1.9.1/test/unit/testcase.rb:17:in `run' | /usr/lib/ruby/1.9.1/minitest/unit.rb:949:in `run' | /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:60:in `test_files' | /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:25:in `assert_roundtrip' | /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:25:in `zip' | /build/buildd-ruby-hpricot_0.8.5-1-ia64-PLeTpi/ruby-hpricot-0.8.5/test/test_preserved.rb:25:in `each' |
