Skip to content

build(workflows): remove stale Node.js version matrix includes in linux_test_install#13231

Draft
Planeshifter wants to merge 1 commit into
developfrom
philipp/ci-fix-linux-test-install-2026-07-02
Draft

build(workflows): remove stale Node.js version matrix includes in linux_test_install#13231
Planeshifter wants to merge 1 commit into
developfrom
philipp/ci-fix-linux-test-install-2026-07-02

Conversation

@Planeshifter

Copy link
Copy Markdown
Member

Description

What is the purpose of this pull request?

This pull request:

  • removes stale include entries from the test_install job's build matrix in linux_test_install.yml.

Failing run: https://github.com/stdlib-js/stdlib/actions/runs/28581985462

Symptom: linux_test_install has failed on every nightly develop run for 30+ consecutive days. The run reports overall conclusion: failure, but zero test_install jobs actually run — only the unrelated Zulip notification job executes.

Root cause: NODE_VERSION was trimmed to ['20', '18', '16'], but include still lists entries for 14, 12, 10, 8, 6, 4, 0.12, 0.10. None of those values match any base matrix combination, so GitHub Actions adds each as a standalone job configuration containing only the keys given in the include entry — missing OS, BUILD_TASK, and PACKAGE_MANAGER. runs-on: ${{ matrix.OS }} then resolves to an empty string, invalidating the job's entire matrix expansion, so no test_install jobs run and the workflow reports failure.

Fix: comment out the eight stale include entries, identical to the pattern already in use in the sibling linux_test.yml and macos_test.yml workflows.

Related Issues

Does this pull request have any related issues?

This pull request has no related issues.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Validation: YAML syntax checked with python3 -c "import yaml; yaml.safe_load(...)". Three independent agent reviews (correctness, regression scope, style) all approved with no blocking findings, confirming the remaining include entries all match existing base combinations and that the comment style matches linux_test.yml/macos_test.yml character-for-character.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

Disclosure

This pull request was prepared by Claude Code as part of an automated CI-failure investigation routine. Root cause was identified from job logs and GitHub Actions matrix semantics, cross-checked against the identical pattern already applied in sibling workflow files, and validated by three independent agent reviews.


@stdlib-js/reviewers


Generated by Claude Code

…nux_test_install`

The `test_install` job in `linux_test_install.yml` failed on every
nightly run on develop for 30+ consecutive days with the workflow
reporting an overall failure while zero `test_install` jobs actually
ran (only the unrelated Zulip notification job executed).

Root cause: `NODE_VERSION` was trimmed to `['20', '18', '16']`, but
the `include` list still listed entries for Node.js 14, 12, 10, 8, 6,
4, 0.12, and 0.10. Since those versions no longer match any base
matrix combination, GitHub Actions adds each as a standalone job
configuration missing `OS`, `BUILD_TASK`, and `PACKAGE_MANAGER`,
which breaks `runs-on: ${{ matrix.OS }}` and invalidates the entire
job's matrix expansion. This commit comments out the stale include
entries, matching the pattern already used in the sibling
`linux_test.yml` and `macos_test.yml` workflows.

Ref: https://github.com/stdlib-js/stdlib/actions/runs/28581985462
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants