Re: Bug#881772: ruby2.5: FTBFS on ppc64(el): stack level too deep
Hi Terceiro,
On 11/15/2017 02:32 PM, Antonio Terceiro wrote:
> Hi,
>
> On Tue, Nov 14, 2017 at 06:16:22PM -0500, Aaron M. Ucko wrote:
>> Source: ruby2.5
>> Version: 2.5.0~preview1-1
>> Severity: important
>> Tags: upstream
>> Justification: fails to build from source
>> User: debian-powerpc@lists.debian.org
>> Usertags: ppc64 ppc64el
>>
>> Builds of ruby2.5 for ppc64el and the non-release architecture ppc64
>> have been failing per the below excerpt from
>>
>> https://buildd.debian.org/status/fetch.php?pkg=ruby2.5&arch=ppc64el&ver=2.5.0%7Epreview1-1&stamp=1510662722&raw=0
>>
>> FTR, the ppc64 log, which exhibits the same error, is at
>>
>> https://buildd.debian.org/status/fetch.php?pkg=ruby2.5&arch=ppc64&ver=2.5.0%7Epreview1-1&stamp=1510663941&raw=0
>>
>> Could you please take a look?
>
> Thanks for reporting.
>
>> Thanks!
>>
>> 1) Error:
>> TestBacktrace#test_caller_lev:
>> SystemStackError: stack level too deep
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:96:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:96:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:93:in `block (2 levels) in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `times'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:92:in `block in test_caller_lev'
>> /<<PKGBUILDDIR>>/test/ruby/test_backtrace.rb:106:in `block in test_caller_lev'
>>
>> Finished tests in 517.516592s, 33.1661 tests/s, 4326.2574 assertions/s.
>> 17164 tests, 2238910 assertions, 0 failures, 1 errors, 85 skips
>>
>> ruby -v: ruby 2.5.0dev (2017-10-10) [powerpc64le-linux-gnu]
>> uncommon.mk:691: recipe for target 'yes-test-almost' failed
>
> Dear POWER porters, would you be able to help with this?
Sorry for not looking at it yet. Unfortunately we will not be able to see it
this week, but I hope to start look at it next week.
Reply to: