Failures in qa/specs/features/browser_ui/4_verify/ci_variable/ui_variable_inheritable...specs | Tests attempt to execute using root user on production

Summary

Tests seem to be misconfigured for running in production

Failing job(s):

• https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/6841491 (job times out)

Jobs executed from parallel test give more details:

• https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/6843353
• https://ops.gitlab.net/gitlab-org/quality/production/-/jobs/6843354

Failing spec(s):

• qa/specs/features/browser_ui/4_verify/ci_variable/ui_variable_non_inheritable_when_forward_pipeline_variables_false_spec.rb
• qa/specs/features/browser_ui/4_verify/ci_variable/ui_variable_inheritable_when_forward_pipeline_variables_true_spec.rb

Corresponding test case(s):

Stack trace

Failure/Error: Runtime::Feature.enable(:ci_trigger_forward_variables)
          
          QA::Page::Validatable::PageValidationError:
            navbar did not appear on QA::Page::Main::Menu as expected

Screenshot / HTML page

Possible fixes

Add feature_flag tag to the individual specs rather than the shared context. There seems to be a bug with how the formatters are applied by spec_helper for shared contexts and examples existing in qa/spec/support, which will be investigated further.