Created attachment 475076 [details] build log $summary
Created attachment 475078 [details] backtrace
As I understand bug 561780#c16 ruby@ team applied ia64 SIGSEGV fix to revbumped ruby only. Namely: >=dev-lang/ruby-2.2.7-r2:2.2 >=dev-lang/ruby-2.3.4-r2:2.3 >=dev-lang/ruby-2.4.1-r2:2.4
ok..since 2.2.6 was the stabilization target I thought it was applied to that version...but you're right @graaff: can you apply it at 2.2.6 so we can stabilize it for ia64?
> @graaff: can you apply it at 2.2.6 so we can stabilize it for ia64? Or another option is to stabilize >=dev-lang/ruby-2.2.7-r2:2.2 on ia64 out of bound earlier to make rest of stabilisation smooth.
(In reply to Sergei Trofimovich from comment #4) > > @graaff: can you apply it at 2.2.6 so we can stabilize it for ia64? > > Or another option is to stabilize >=dev-lang/ruby-2.2.7-r2:2.2 on ia64 out > of bound earlier to make rest of stabilisation smooth. Stabling dev-lang/ruby-2.2.7-r2 early for ia64 would be my preference.
(In reply to Hans de Graaff from comment #5) > (In reply to Sergei Trofimovich from comment #4) > > > @graaff: can you apply it at 2.2.6 so we can stabilize it for ia64? > > > > Or another option is to stabilize >=dev-lang/ruby-2.2.7-r2:2.2 on ia64 out > > of bound earlier to make rest of stabilisation smooth. > > Stabling dev-lang/ruby-2.2.7-r2 early for ia64 would be my preference. Cool! Stabled ruby22 bundle from bug #615818 on ia64 (=dev-lang/ruby-2.2.7-r2)