Pull Request resolves #46925.

• I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

The tests-system job in ci.yml runs in a matrix with 12 combinations (6 configs × 2 browsers), but the upload-artifact step uses a static artifact name system-test-output.

With actions/upload-artifact@v4, duplicate artifact names cause upload failures (unlike v3, which merged them). Only the first completed matrix run's artifact gets saved; the rest fail.

Changes made:

• Made the artifact name unique per matrix combination: system-test-output-${{ matrix.browser }}-${{ matrix.config.test_group }}
• Fixed a minor typo in the step name: "Archive test results results" → "Archive test results"

Reference: https://github.com/actions/upload-artifact/blob/main/docs/MIGRATION.md#multiple-uploads-to-the-same-named-artifact

Testing Instructions

1. Open .github/workflows/ci.yml, line 358-366
2. Verify the step name reads Archive test results (not "results results")
3. Verify the artifact name is system-test-output-${{ matrix.browser }}-${{ matrix.config.test_group }}
4. Trigger a CI run and confirm all 12 matrix combinations upload artifacts without conflicts

Actual result BEFORE applying this Pull Request

All 12 matrix jobs in tests-system attempt to upload an artifact with the same static name system-test-output. With upload-artifact@v4, this causes upload failures for all but the first job to complete.

Expected result AFTER applying this Pull Request

Each matrix combination uploads its artifact with a unique name (e.g., system-test-output-chrome-cmysqlmax, system-test-output-edge-cpostgres), preventing upload conflicts.

Link to documentations

Please select:

• Documentation link for guide.joomla.org:

• No documentation changes for guide.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed