Doubles the max_duration time to wait for pipeline status widget

qa/qa/page/merge_request/show.rb

@@ -202,7 +202,7 @@ module QA
 
         def has_pipeline_status?(text)
           # Pipelines can be slow, so we wait a bit longer than the usual 10 seconds
-          wait_until(sleep_interval: 5, reload: false) do
+          wait_until(max_duration: 120, sleep_interval: 5, reload: true) do
             has_element?(:merge_request_pipeline_info_content, text: text, wait: 15 )
           end
         end

qa/qa/specs/features/ee/browser_ui/4_verify/new_discussion_not_dropping_merge_trains_mr_spec.rb

@@ -53,11 +53,9 @@ module QA
         it 'does not drop MR', testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/quality/test_cases/1250' do
           start_discussion
 
-          Support::Retrier.retry_until(max_attempts: 3, sleep_interval: 3) do
-            Page::MergeRequest::Show.perform do |show|
-              show.has_pipeline_status?('passed')
-              expect(show).to be_merged
-            end
+          Page::MergeRequest::Show.perform do |show|
+            show.has_pipeline_status?('passed')
+            expect(show).to be_merged
           end
         end
 

qa/qa/specs/features/ee/browser_ui/4_verify/pipelines_for_merged_results_and_merge_trains_spec.rb

@@ -63,30 +63,26 @@ module QA
       it 'creates a pipeline with merged results', testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/quality/test_cases/1517' do
         merge_request.visit!
 
-        Support::Retrier.retry_until(max_attempts: 3, sleep_interval: 3) do
-          Page::MergeRequest::Show.perform do |show|
-            expect(show).to have_pipeline_status('passed'), 'Expected the merge request pipeline to pass.'
+        Page::MergeRequest::Show.perform do |show|
+          expect(show).to have_pipeline_status('passed'), 'Expected the merge request pipeline to pass.'
 
-            # The default option is to merge via merge train,
-            # but that is covered by the 'merges via a merge train' test
-            show.skip_merge_train_and_merge_immediately
+          # The default option is to merge via merge train,
+          # but that is covered by the 'merges via a merge train' test
+          show.skip_merge_train_and_merge_immediately
 
-            expect(show).to be_merged, "Expected content 'The changes were merged' but it did not appear."
-          end
+          expect(show).to be_merged, "Expected content 'The changes were merged' but it did not appear."
         end
       end
 
       it 'merges via a merge train', testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/quality/test_cases/1518' do
         merge_request.visit!
 
-        Support::Retrier.retry_until(max_attempts: 3, sleep_interval: 3) do
-          Page::MergeRequest::Show.perform do |show|
-            expect(show).to have_pipeline_status('passed'), 'Expected the merge request pipeline to pass.'
+        Page::MergeRequest::Show.perform do |show|
+          expect(show).to have_pipeline_status('passed'), 'Expected the merge request pipeline to pass.'
 
-            show.merge_via_merge_train
+          show.merge_via_merge_train
 
-            expect(show).to be_merged, "Expected content 'The changes were merged' but it did not appear."
-          end
+          expect(show).to be_merged, "Expected content 'The changes were merged' but it did not appear."
         end
       end
     end