[#84867] [Ruby trunk Bug#14357] thread_safe tests suite segfaults — v.ondruch@...

Issue #14357 has been reported by vo.x (Vit Ondruch).

11 messages 2018/01/15
[#85364] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults — Eric Wong <normalperson@...> 2018/02/03

v.ondruch@tiscali.cz wrote:

[#84980] [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — hsbt@...

Issue #13618 has been updated by hsbt (Hiroshi SHIBATA).

10 messages 2018/01/23
[#85012] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — Eric Wong <normalperson@...> 2018/01/23

hsbt@ruby-lang.org wrote:

[ruby-core:85272] Re: [ruby-changes:49998] normal:r62116 (trunk): ruby.h: relax rb_funcall check on extra args for clang

From: Eric Wong <normalperson@...>
Date: 2018-01-31 01:55:41 UTC
List: ruby-core #85272
Koichi Sasada <ko1@atdot.net> wrote:
> This commit causes a bug on parallel tests.
> 
> http://ci.rvm.jp/latest
> 
> for example:
> http://ci.rvm.jp/results/trunk_gcc4@silicon-docker/466645
> 
> >test_all             /home/ko1/ruby/src/trunk_gcc4/lib/rubygems/core_ext/kernel_require.rb:59:in `require': undefined class/module TestFuncall::Relay (ArgumentError)
> >	/home/ko1/ruby/src/trunk_gcc4/lib/rubygems/core_ext/kernel_require.rb:59:in `require'
> >	/home/ko1/ruby/src/trunk_gcc4/test/-ext-/funcall/test_funcall.rb:5:in `<class:TestFuncall>'
> >	/home/ko1/ruby/src/trunk_gcc4/test/-ext-/funcall/test_funcall.rb:4:in `<top (required)>'
> >	/home/ko1/ruby/src/trunk_gcc4/lib/rubygems/core_ext/kernel_require.rb:59:in `require'
> >	/home/ko1/ruby/src/trunk_gcc4/lib/rubygems/core_ext/kernel_require.rb:59:in `require'
> >	/home/ko1/ruby/src/trunk_gcc4/test/lib/test/unit/parallel.rb:116:in `run'
> >	/home/ko1/ruby/src/trunk_gcc4/test/lib/test/unit/parallel.rb:207:in `<main>'
> >running file: /home/ko1/ruby/src/trunk_gcc4/test/-ext-/funcall/test_funcall.rb
> 
> I'm not sure why it is raised and I can't reproduce it on my environment.
> 
> Sometimes it successes. Maybe timing issue.
> http://ci.rvm.jp/results/trunk_gcc4@silicon-docker
> 
> Do you have any idea?

Looks like an old version of funcall.so; maybe we have a race
condition in common.mk?

Do you finish "make" before "make test-all"?

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next