QA failures on gprd-cny

Overview

Pipeline:

1) Plan Epics milestone dates API updates epic dates when removing issue
     [31mGot 2 failures from failure aggregation block.[0m
     [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:190:in `expect_epic_to_have_updated_dates'[0m
     [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:81:in `block (3 levels) in <module:QA>'[0m
     [36m# /home/gitlab/spec/support/fast_quarantine.rb:22:in `block (2 levels) in <top (required)>'[0m
     [36m# ./qa/specs/runner.rb:124:in `run_rspec'[0m
     [36m# ./qa/specs/runner.rb:32:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/template.rb:63:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/bootable.rb:52:in `launch!'[0m

     1.1) [31mFailure/Error:[0m
          [31m  expect { epic.reload!.start_date }[0m
          [31m    .to eventually_eq(new_milestone_start_date).within(wait_args)[0m
          [31m[0m
          [31m  Wait failed after 10 seconds:[0m
          [31m[0m
          [31m  expected to eventually equal: nil[0m
          [31m[0m
          [31m  last attempt was: "2026-01-15"[0m
          [31m[0m
          [31m  Diff:[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:191:in `block in expect_epic_to_have_updated_dates'[0m

     1.2) [31mFailure/Error:[0m
          [31m  expect { epic.reload!.due_date }[0m
/builds/gitlab-org/quality/production/.gems/bin/gitlab-qa: Command `docker run -t --rm --net=bridge --env QA_CAN_TEST_GIT_PROTOCOL_V2="$QA_CAN_TEST_GIT_PROTOCOL_V2" ...` failed! [31m✘[0m (Gitlab::QA::Support::ShellCommand::StatusError)
/builds/gitlab-org/quality/production/.gems/bin/gitlab-qa: Command `docker run -t --rm --net=bridge --env QA_CAN_TEST_GIT_PROTOCOL_V2="$QA_CAN_TEST_GIT_PROTOCOL_V2" ...` failed! [31m✘[0m (Gitlab::QA::Support::ShellCommand::StatusError)
          [31m    .to eventually_eq(new_milestone_due_date).within(wait_args)[0m
          [31m[0m
          [31m  Wait failed after 10 seconds:[0m
          [31m[0m
          [31m  expected to eventually equal: nil[0m
          [31m[0m
          [31m  last attempt was: "2026-02-04"[0m
          [31m[0m
          [31m  Diff:[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:193:in `block in expect_epic_to_have_updated_dates'[0m

  2) Plan Epics milestone dates API updates epic dates when adding another issue
     [31mGot 2 failures from failure aggregation block.[0m
     [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:48:in `block (3 levels) in <module:QA>'[0m
     [36m# /home/gitlab/spec/support/fast_quarantine.rb:22:in `block (2 levels) in <top (required)>'[0m
     [36m# ./qa/specs/runner.rb:124:in `run_rspec'[0m
     [36m# ./qa/specs/runner.rb:32:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/template.rb:63:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/bootable.rb:52:in `launch!'[0m

     2.1) [31mGot 2 failures from failure aggregation block.[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:190:in `expect_epic_to_have_updated_dates'[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:49:in `block (4 levels) in <module:QA>'[0m

          2.1.1) [31mFailure/Error:[0m
                 [31m  expect { epic.reload!.start_date }[0m
                 [31m    .to eventually_eq(new_milestone_start_date).within(wait_args)[0m
                 [31m[0m
                 [31m  Wait failed after 10 seconds:[0m
                 [31m[0m
                 [31m  expected to eventually equal: "2025-10-07"[0m
                 [31m[0m
                 [31m  last attempt was: "2026-01-15"[0m
                 [31m[0m
                 [31m  Diff:[0m
                 [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:191:in `block in expect_epic_to_have_updated_dates'[0m

          2.1.2) [31mFailure/Error:[0m
                 [31m  expect { epic.reload!.due_date }[0m
                 [31m    .to eventually_eq(new_milestone_due_date).within(wait_args)[0m
                 [31m[0m
                 [31m  Wait failed after 10 seconds:[0m
                 [31m[0m
                 [31m  expected to eventually equal: "2026-03-06"[0m
                 [31m[0m
                 [31m  last attempt was: "2026-02-04"[0m
                 [31m[0m
                 [31m  Diff:[0m
                 [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:193:in `block in expect_epic_to_have_updated_dates'[0m

     2.2) [31mGot 2 failures from failure aggregation block.[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:212:in `expect_epic_to_have_updated_milestone'[0m
          [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:52:in `block (4 levels) in <module:QA>'[0m

          2.2.1) [31mFailure/Error: expect(epic.start_date_sourcing_milestone[:id]).to have_content(milestone.id)[0m
                 [31m  expected to find text "6160744" in "gid://gitlab/Milestone/6160743"[0m
                 [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:213:in `block in expect_epic_to_have_updated_milestone'[0m

          2.2.2) [31mFailure/Error: expect(epic.due_date_sourcing_milestone[:id]).to have_content(milestone.id)[0m
                 [31m  expected to find text "6160744" in "gid://gitlab/Milestone/6160743"[0m
                 [36m# ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:214:in `block in expect_epic_to_have_updated_milestone'[0m

Finished in 1 minute 21.05 seconds (files took 1.66 seconds to load)
[31m2 examples, 2 failures[0m

Failed examples:

[31mrspec ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:57[0m [36m# Plan Epics milestone dates API updates epic dates when removing issue[0m
[31mrspec ./qa/specs/features/ee/api/2_plan/epics_milestone_dates_spec.rb:35[0m [36m# Plan Epics milestone dates API updates epic dates when adding another issue[0m

Pipeline:

1) Software Supply Chain Security basic user login user logs in using basic credentials and logs out
     [31mFailure/Error: Flow::Login.sign_in[0m
     [31m[0m
     [31mQA::Runtime::Canary::CanaryValidationError:[0m
     [31m  gitlab_canary=true cookie was set in browser but 'Next' badge was not shown on UI[0m
     [36m# ./qa/runtime/canary.rb:22:in `validate_canary!'[0m
     [36m# ./qa/page/main/login.rb:253:in `sign_in_using_gitlab_credentials'[0m
     [36m# ./qa/page/main/login.rb:78:in `block in sign_in_using_credentials'[0m
     [36m# ./qa/page/main/login.rb:67:in `sign_in_using_credentials'[0m
     [36m# ./qa/flow/login.rb:28:in `block in sign_in'[0m
     [36m# ./qa/scenario/actable.rb:16:in `perform'[0m
     [36m# ./qa/flow/login.rb:22:in `sign_in'[0m
     [36m# ./qa/specs/features/browser_ui/10_software_supply_chain_security/login/log_in_spec.rb:8:in `block (3 levels) in <module:QA>'[0m
     [36m# /home/gitlab/spec/support/fast_quarantine.rb:22:in `block (2 levels) in <top (required)>'[0m
     [36m# ./qa/specs/runner.rb:124:in `run_rspec'[0m
     [36m# ./qa/specs/runner.rb:32:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/template.rb:63:in `perform'[0m
     [36m# ./qa/scenario/template.rb:10:in `block in perform'[0m
     [36m# ./qa/scenario/template.rb:8:in `perform'[0m
     [36m# ./qa/scenario/bootable.rb:52:in `launch!'[0m

Finished in 28.48 seconds (files took 2.07 seconds to load)
[31m1 example, 1 failure[0m

Failed examples:

[31mrspec ./qa/specs/features/browser_ui/10_software_supply_chain_security/login/log_in_spec.rb:6[0m [36m# Software Supply Chain Security basic user login user logs in using basic credentials and logs out[0m