Ruby 3.3 support?

[mikebaldry]

I tried running our test suite against Ruby 3.3.1 today and the tests just never finished on multiple workers. They were just sitting there doing nothing and I killed the build after an hour.

I initially thought this was something Ruby related, but after removing Knapsack from our CI scripts, everything works.

[3v0k4]

Hi Mike, I'm sorry for the troubles.

Knapsack is tested with Ruby 3.3.1—I just double checked that CircleCI resolves 3.3 to 3.3.1.

Could you please send an email to support@knapsackpro.com with the following info:

• commit hash of the build; I believe it starts with 808fc0...
• CI terminal output of one of the nodes that hangs—do they all hang in the same way?

Here are a couple of strategies you could use to debug the issue:

• Run a build with KNAPSACK_PRO_LOG_LEVEL=debug and check the logs; please send one over if you do this.
• Print the backtrace of the thread(s) (see below).

To print the backtrace(s) you can do the following:

1) Add the following to spec_helper.rb:

puts "Process pid: #{Process.pid}"

trap 'USR1' do
  threads = Thread.list

  puts
  puts "=" * 80
  puts "Received USR1 signal; printing all #{threads.count} thread backtraces."

  threads.each do |thr|
    description = thr == Thread.main ? "Main thread" : thr.inspect
    puts
    puts "#{description} backtrace: "
    puts thr.backtrace.join("\n")
  end

  puts "=" * 80
end

2) Run Knapsack with timeout --signal=USR1 30 bundle exec rake "knapsack_pro:queue:rspec[--format d]"

Notice that 30 is in seconds, so you may want to increase that number to make sure timeout sends USR1 when the process is stuck and not before.

3) Check the logs for information. Please share them with us if you attempt this.

[mikebaldry]

I'm running through these steps now, I'll email over to you with my findings.

Thanks

[ArturT]

Summary after private conversation.

Disabling YJIT helps.

The issue might be related to YJIT:

• https://github.com/ruby/ruby/pull/10787

[ArturT]

I'm closing this issue because disabling YJIT helped.

@mikebaldry I've replied in our private conversation. Please let me know if you need more help.