Skip to content

Flaky spec: ee/spec/features/epic_boards/epic_boards_spec.rb:120 # epic boards display epics in board moving updates weight of both lists

Summary

Master-broken incidents:

Job #3870813976 failed for c7e1ffcc:

Failures:
  1) epic boards display epics in board moving updates weight of both lists
     Got 2 failures:
     1.1) Failure/Error: expect(find('[data-testid="board-list-header"] [data-testid="weight"]')).to have_content(issue_with_weight.weight)
            expected to find text "2" in "0"
            Timeout (30s) reached while running a waiting Capybara finder.
            Consider using a non-waiting finder.
            See https://www.cloudbees.com/blog/faster-rails-tests
          # ./ee/spec/features/epic_boards/epic_boards_spec.rb:137:in `block (4 levels) in <main>'
          # ./ee/spec/features/epic_boards/epic_boards_spec.rb:136:in `block (3 levels) in <main>'
          # ./spec/spec_helper.rb:506:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:498:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:494:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:59:in `with_raw_context'
          # ./spec/spec_helper.rb:494:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:242:in `block (2 levels) in <top (required)>'
          # ./spec/support/sidekiq.rb:21:in `block (3 levels) in <main>'
          # ./spec/support/sidekiq.rb:8:in `gitlab_sidekiq_inline'
          # ./spec/support/sidekiq.rb:21:in `block (2 levels) in <main>'
          # ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
          # ./spec/support/database/prevent_cross_joins.rb:108:in `block (3 levels) in <main>'
          # ./spec/support/database/prevent_cross_joins.rb:62:in `with_cross_joins_prevented'
          # ./spec/support/database/prevent_cross_joins.rb:108:in `block (2 levels) in <main>'
     1.2) Failure/Error: expect(find('[data-testid="board-list-header"] [data-testid="weight"]')).to have_content('0')
            expected to find text "0" in "2"
            Timeout (30s) reached while running a waiting Capybara finder.
            Consider using a non-waiting finder.
            See https://www.cloudbees.com/blog/faster-rails-tests
          # ./ee/spec/features/epic_boards/epic_boards_spec.rb:141:in `block (4 levels) in <main>'
          # ./ee/spec/features/epic_boards/epic_boards_spec.rb:140:in `block (3 levels) in <main>'
          # ./spec/spec_helper.rb:506:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:498:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:494:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:59:in `with_raw_context'
          # ./spec/spec_helper.rb:494:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:242:in `block (2 levels) in <top (required)>'
          # ./spec/support/sidekiq.rb:21:in `block (3 levels) in <main>'
          # ./spec/support/sidekiq.rb:8:in `gitlab_sidekiq_inline'
          # ./spec/support/sidekiq.rb:21:in `block (2 levels) in <main>'
          # ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
          # ./spec/support/database/prevent_cross_joins.rb:108:in `block (3 levels) in <main>'
          # ./spec/support/database/prevent_cross_joins.rb:62:in `with_cross_joins_prevented'
          # ./spec/support/database/prevent_cross_joins.rb:108:in `block (2 levels) in <main>'
Finished in 1 minute 18.94 seconds (files took 1 minute 13.6 seconds to load)
1 example, 1 failure
Failed examples:
rspec ./ee/spec/features/epic_boards/epic_boards_spec.rb:120 # epic boards display epics in board moving updates weight of both lists
[TEST PROF INFO] Time spent in factories: 00:02.337 (2.84% of total time)

Steps to reproduce

Please refer to Flaky tests documentation to learn more about how to reproduce them.

Proposed Resolution

Please refer to the Resolution guidance to learn more about resolution of broken master.

Once the flaky failure has been fixed on the default branch, open merge requests to cherry-pick the fix to the active stable branches.