Tukukkk

After upgrading rails from 4.2 to 5.2 my test gets stuck on a request while it is working in development server I'm getting following failure on running test suit.

Failures:



  1) cold end overview shows cold end stats

     Failure/Error: example.run



     RuntimeError:

       Requests did not finish in 60 seconds

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara/server.rb:94:in `rescue in wait_for_pending_requests'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara/server.rb:91:in `wait_for_pending_requests'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara/session.rb:130:in `reset!'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara.rb:314:in `block in reset_sessions!'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara.rb:314:in `reverse_each'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara.rb:314:in `reset_sessions!'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara/rspec.rb:22:in `block (2 levels) in <top (required)>'

     # ./spec/spec_helper.rb:43:in `block (3 levels) in <top (required)>'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/database_cleaner-1.6.2/lib/database_cleaner/generic/base.rb:16:in `cleaning'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/database_cleaner-1.6.2/lib/database_cleaner/base.rb:98:in `cleaning'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/database_cleaner-1.6.2/lib/database_cleaner/configuration.rb:86:in `block (2 levels) in cleaning'

     # /home/asnad/.rvm/gems/ruby-2.5.0/gems/database_cleaner-1.6.2/lib/database_cleaner/configuration.rb:87:in `cleaning'

     # ./spec/spec_helper.rb:37:in `block (2 levels) in <top (required)>'

     # ------------------

     # --- Caused by: ---

     # Timeout::Error:

     #   execution expired

     #   /home/asnad/.rvm/gems/ruby-2.5.0/gems/capybara-2.18.0/lib/capybara/server.rb:92:in `sleep'



Top 1 slowest examples (62.59 seconds, 97.0% of total time):

  cold end overview shows cold end stats

    62.59 seconds ./spec/features/cold_end_overview_spec.rb:13



Finished in 1 minute 4.51 seconds (files took 4.15 seconds to load)

1 example, 1 failure

my spec_helper.rb has configurations

RSpec.configure do |config|

  config.include FactoryBot::Syntax::Methods



  config.around(:each) do |example|

    DatabaseCleaner[:active_record].clean_with(:truncation)



    DatabaseCleaner.cleaning do

      if example.metadata.key?(:js) || example.metadata[:type] == :feature

        # VCR.configure { |c| c.ignore_localhost = true }

        WebMock.allow_net_connect!

        VCR.turn_off!

        VCR.eject_cassette

        example.run

      else

        # WebMock.disable_net_connect!

        VCR.turn_on!

        cassette_name = example.metadata[:full_description]

                               .split(/s+/, 2)

                               .join('/')

                               .underscore.gsub(/[^w/]+/, '_')

        # VCR.configure { |c| c.ignore_localhost = false }

        VCR.use_cassette(cassette_name) { example.run }

        VCR.turn_off!

        WebMock.allow_net_connect!

      end

    end

  end



  config.expect_with :rspec do |expectations|

    expectations.include_chain_clauses_in_custom_matcher_descriptions = true

  end



  config.mock_with :rspec do |mocks|

    mocks.verify_partial_doubles = true

  end



  config.filter_run :focus

  config.run_all_when_everything_filtered = true



  config.example_status_persistence_file_path = "spec/examples.txt"



  if config.files_to_run.one?

    config.default_formatter = 'doc'

  end



  # Print the 10 slowest examples and example groups at the

  # end of the spec run, to help surface which specs are running

  # particularly slow.

  config.profile_examples = 10



  # Run specs in random order to surface order dependencies. If you find an

  # order dependency and want to debug it, you can fix the order by providing

  # the seed, which is printed after each run.

  #     --seed 1234

  config.order = :random



  # Seed global randomization in this process using the `--seed` CLI option.

  # Setting this allows you to use `--seed` to deterministically reproduce

  # test failures related to randomization by passing the same `--seed` value

  # as the one that triggered the failure.

  Kernel.srand config.seed

end



# Selenium::WebDriver.logger.level = :debug

# Selenium::WebDriver.logger.output = 'selenium.log'

Capybara.register_driver :selenium_chrome_headless do |app|

  capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(chromeOptions: { args: %w[headless no-sandbox disable-dev-shm-usage disable-gpu window-size=1200,1500] }, loggingPrefs: { browser: 'ALL' })

  Capybara::Selenium::Driver.new(app, browser: :chrome, desired_capabilities: capabilities)

end



Chromedriver.set_version '2.39'



Capybara.javascript_driver = :selenium_chrome_headless

Capybara::Screenshot.prune_strategy = :keep_last_run

in my spec the line sign_in current_user takes too much time actually it redirects to a page and do not get response even long time while it is working on development environment.
what can be the reason if you need anything else please comment.