Flaky test: spec/features/broadcast_messages_spec.rb[1:3:2:2] # Broadcast Messages notification type behaves like a dismissable Broadcast Messages broadcast message is still hidden after refresh

Summary

Master-broken incident: gitlab-org/quality/engineering-productivity/master-broken-incidents#873 (closed)

Job #3753345433 failed for 2413c01d:

Failures:
  1) Broadcast Messages notification type behaves like a dismissable Broadcast Messages broadcast message is still hidden after refresh
     Got 0 failures and 2 other errors:
     Shared Example Group: "a dismissable Broadcast Messages" called from ./spec/features/broadcast_messages_spec.rb:83
     1.1) Failure/Error: raise "Condition not met: #{condition_name}"
          RuntimeError:
            Condition not met: Complete setting cookie
          # ./spec/support/helpers/wait_helpers.rb:16:in `block in wait_for'
          # ./spec/support/helpers/wait_helpers.rb:9:in `loop'
          # ./spec/support/helpers/wait_helpers.rb:9:in `wait_for'
          # ./spec/support/helpers/cookie_helper.rb:31:in `wait_for_cookie_set'
          # ./spec/features/broadcast_messages_spec.rb:40:in `block (3 levels) in <main>'
          # ./spec/spec_helper.rb:509:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:501:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:497:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:59:in `with_raw_context'
          # ./spec/spec_helper.rb:497:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
          # ./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: raise JSConsoleError, message
          JSConsoleError:
            Unexpected browser console output:
            security - Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
            https://localhost/com.snowplowanalytics.snowplow/tp2 - Failed to load resource: net::ERR_CONNECTION_REFUSED
          # ./spec/support/capybara.rb:221:in `block (2 levels) in <main>'
          # ./spec/spec_helper.rb:509:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:501:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:497:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:59:in `with_raw_context'
          # ./spec/spec_helper.rb:497:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:239:in `block (2 levels) in <top (required)>'
          # ./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.14 seconds (files took 1 minute 12.79 seconds to load)
2 examples, 1 failure
Failed examples:
rspec './spec/features/broadcast_messages_spec.rb[1:3:2:2]' # Broadcast Messages notification type behaves like a dismissable Broadcast Messages broadcast message is still hidden after refresh

broadcast_messages_notification_type_behaves_like_a_dismissable_broadcast_messages_broadcast_message_is_still_hidden_after_refresh__1_

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.