ruby2.3 test failures on s390x

[Matthias Klose]

seen with https://launchpad.net/ubuntu/+source/ruby2.3/2.3.0-4/+build/9302935

test_thread.rb ...Fstderr output is not empty
   bootstraptest.tmp.rb:4:in `initialize': can't create Thread: Resource temporarily unavailable (ThreadError)
           from bootstraptest.tmp.rb:4:in `new'
           from bootstraptest.tmp.rb:4:in `block (2 levels) in <main>'
           from bootstraptest.tmp.rb:3:in `each'
           from bootstraptest.tmp.rb:3:in `map'
           from bootstraptest.tmp.rb:3:in `block in <main>'
           from bootstraptest.tmp.rb:2:in `times'
           from bootstraptest.tmp.rb:2:in `<main>'
uncommon.mk:581: recipe for target 'yes-btest-ruby' failed
make[1]: *** [yes-btest-ruby] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: make -j4 test returned exit code 2
debian/rules:53: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

[Brian Murray (brian-murray)]

Hello Matthias, or anyone else affected,

Accepted ruby2.3 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ruby2.3/2.3.1-2~16.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Matthias Klose (doko)]

the 2.3.1 upload to xenial fixed these test failures

[Launchpad Janitor (janitor)]

This bug was fixed in the package ruby2.3 - 2.3.1-2~16.04

---------------
ruby2.3 (2.3.1-2~16.04) xenial-proposed; urgency=medium

  * SRU: LP: #1589271, backport 2.3.1 to 16.04 LTS.
  * Fixes tests on s390x. LP: #1556783.

ruby2.3 (2.3.1-2) unstable; urgency=medium

  [ Antonio Terceiro ]
  * debian/tests/known-failures.txt: remove test that now passes
    (test/rinda/test_rinda.rb)
  * debian/rules: enable bindnow hardening option (Closes: #822288)
  * debian/copyright: update and simplify copyright annotations for Unicode
    files under enc/trans/JIS/
  * Bump Standards-Version to 3.9.8 (no changes needed)

  [ Christian Hofstaedtler ]
  * Stop providing ruby-interpreter. Only packages providing
    /usr/bin/ruby can be a credible provider of ruby-interpreter.
    (Closes: #822072)
  * Raise priority to "optional", now that ruby2.2 is gone, although
    the value of this change is unclear. (Closes: #822911)
  * Apply patch from Reiner Herrmann <email address hidden> to help with
    reproducibility of mkmf.rb using packages. (Closes: #825569)

ruby2.3 (2.3.1-1) unstable; urgency=medium

  * Call make install-doc, install-nodoc with V=1, for diagnosing
    build failures.
  * New upstream TEENY version.

 -- Matthias Klose <email address hidden> Sun, 05 Jun 2016 17:50:45 +0200

[Chris J Arges (arges)]

The verification of the Stable Release Update for ruby2.3 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.