Closed chrishough closed 7 months ago
I also encountered the same Issue. Is it unresolved?
The global config for Sidekiq doesn't actually set anything in the job specific options which is what be_retryable
specifically tests. The Max Retries config is only leveraged directly in the job retry code in Sidekiq (and the job setting takes precedence naturally).
The matcher for
it { is_expected.to be_retryable 10 }
is not picking up the:max_retries: 10
in theconfig/sidekiq.yml
file.