RSpec failure: spec/features/projects/work_items/work_item_spec.rb:37

Summary

Recent master:broken Incident: gitlab-org/quality/engineering-productivity/master-broken-incidents#1566 (closed)

Failures:
  1) Work item for signed in user behaves like work items assignees successfully assigns the current user by searching
     Got 1 failure and 1 other error:
     Shared Example Group: "work items assignees" called from ./spec/features/projects/work_items/work_item_spec.rb:37
     1.1) Failure/Error: expect(work_item.assignees).to include(user)
            expected #<ActiveRecord::Associations::CollectionProxy [#<User id:385 @namespace1>]> to include #<User id:386 @user1>
            Diff:
            @@ -1 +1 @@
            -[#<User id:386 @user1>]
            +[#<User id:385 @namespace1>]
          # ./spec/support/shared_examples/features/work_items_shared_examples.rb:151:in `block (2 levels) in <main>'
          # ./spec/spec_helper.rb:419:in `block (3 levels) in <top (required)>'
          # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
          # ./spec/spec_helper.rb:411:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:407:in `block (3 levels) in <top (required)>'
          # ./lib/gitlab/application_context.rb:61:in `with_raw_context'
          # ./spec/spec_helper.rb:407:in `block (2 levels) in <top (required)>'
          # ./spec/spec_helper.rb:242:in `block (2 levels) in <top (required)>'
          # ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
          # ./spec/support/fast_quarantine.rb:39: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 25.22 seconds (files took 48.84 seconds to load)
1 example, 1 failure

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.