ruby2.3 test/build failures (was: Re: [DRE-maint] Bug#827220: ruby-kgio FTBFS on hppa architecture)

Christian Hofstaedtler <[email protected]> Fri, 17 Jun 2016 20:20:55 +0200
Newsgroups	gmane.linux.debian.devel.ruby,gmane.linux.debian.ports.arm,gmane.linux.debian.ports.mips
Message-ID	<20160617182055.GA42484@sx>
Hi everybody,

* Christian Hofstaedtler <[email protected]> [160617 20:06]:
> We've recently enabled `make check` in the ruby2.3 builds (prompted
> by this thread).
> 
> I'd love any help with diagnosing/finding fixes for the resulting
> build failures:
> 
>    https://buildd.debian.org/status/package.php?p=ruby2.3&suite=sid

To give everyone an overview of the current issues (on release archs), I've
roughly grouped the test failures by topic and arch below.

As some of these tests point to serious issues, just disabling is
not the "correct" fix there.

Current Failures:


[armel, mips, mipsel, mips64el, powerpcspe, sparc64]
  TestArray#test_permutation_stack_error [/«PKGBUILDDIR»/test/ruby/test_array.rb:1826]:
  pid XXX killed by SIGTERM (signal 15)
(On mips/mipsel: SIGABRT (signal 6))


[mipsel]
  TestNum2int#test_num2int [/«PKGBUILDDIR»/test/-ext-/num2int/test_num2int.rb:143]:
  NUM2INT(-2147483648.5).
  <"-2147483648"> expected but was <"2147483647">.
  TestNum2int#test_num2long [/«PKGBUILDDIR»/test/-ext-/num2int/test_num2int.rb:161]:
  NUM2LONG(-2147483648.5).
  <"-2147483648"> expected but was <"2147483647">.
  TestNum2int#test_num2uint [/«PKGBUILDDIR»/test/-ext-/num2int/test_num2int.rb:154]:
  NUM2UINT(-2147483648.5).
  <"2147483648"> expected but was <"2147483647">.
  TestNum2int#test_num2ulong [/«PKGBUILDDIR»/test/-ext-/num2int/test_num2int.rb:177]:
  NUM2ULONG(-2147483648.5).
  <"2147483648"> expected but was <"2147483647">.


[mipsel]
  TestThread#test_thread_name [/«PKGBUILDDIR»/test/ruby/test_thread.rb:1061]:
  <"#<TestThread::Thread:0x6963ab0@/«PKGBUILDDIR»/test/ruby/test_thread.rb:1054 run>"> expected but was
  <"#<TestThread::Thread:0x6963ab0@/«PKGBUILDDIR»/test/ruby/test_thread.rb:1054 sleep>">.


[amd64]
  TestProcess#test_threading_works_after_exec_fail:
  Timeout::Error: execution expired
      /«PKGBUILDDIR»/test/ruby/test_process.rb:2234:in `gets'
      /«PKGBUILDDIR»/test/ruby/test_process.rb:2234:in `block in test_threading_works_after_exec_fail'
      /«PKGBUILDDIR»/lib/timeout.rb:106:in `timeout'
      /«PKGBUILDDIR»/test/ruby/test_process.rb:2217:in `test_threading_works_after_exec_fail'
(I have not seen this one on my build host yet and also not on the
-3 build, so maybe this is a transient problem.)


[mips]

  TestGc#test_gc_parameter:
  Timeout::Error: execution of assert_in_out_err expired
  pid 27560 killed by SIGTERM (signal 15)
  | 
  
      /«PKGBUILDDIR»/test/ruby/test_gc.rb:215:in `test_gc_parameter'
  
  TestGc#test_interrupt_in_finalizer:
  Timeout::Error: execution of assert_in_out_err expired
  pid 27568 killed by SIGABRT (signal 6)
  | 
  | -e: Interrupt
  | -e:16: [BUG] Segmentation fault at 0x0050e8
  | ruby 2.3.1p112 (2016-04-26) [mips-linux-gnu]
  | 
  | -- Control frame information -----------------------------------------------
  | c:0004 p:0000 s:0009 e:000008 BLOCK  -e:16 [FINISH]
  | c:0003 p:---- s:0007 e:000006 CFUNC  :times
  | c:0002 p:0010 s:0004 e:000003 BLOCK  -e:16 [FINISH]
  | c:0001 p:0000 s:0002 E:000a48 (none) [FINISH]
  | 
  | -- Ruby level backtrace information ----------------------------------------
  | -e:16:in `block in <main>'
  | -e:16:in `times'
  | -e:16:in `block (2 levels) in <main>'
  | 
  | -- C level backtrace information -------------------------------------------
  | /«PKGBUILDDIR»/libruby-2.3.so.2.3.0(rb_print_backtrace+0x30) [0x774e583c]
  

There are additional failures on non-release archs, but let's fix
the release archs first.

  C.

-- 
 ,''`.  Christian Hofstaedtler <[email protected]>
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
signature.asc (application/pgp-signature, 801 B)