Environment
ESLint version: ^9.11.1
@eslint/css version: HEAD
Node version: lts/* (currently 22.14.0)
npm version: 10.9.2
Operating System: ubuntu-latest / ubuntu-24.04
What problem do you want to solve?
In the workflow .github/workflows/ci.yml with job test the strategy.matrix uses the default strategy.fail-fast value of true so that any failed matrix jobs cause the whole higher level test job to be cancelled.
This is currently the case in https://github.com/eslint/css/actions/workflows/ci.yml due to eslint/csstree#27.
In general it is more convenient to allow all matrix jobs to run to their own independent completion. This gives a better overview of where failures are occurring. For example, they may affect all configurations, certain Node.js versions or certain operating system only.
What do you think is the correct solution?
In the workflow .github/workflows/ci.yml add fail-fast: true to the matrix parameters.
Participation
Additional comments
No response
Environment
ESLint version:
^9.11.1@eslint/css version: HEAD
Node version:
lts/*(currently22.14.0)npm version:
10.9.2Operating System: ubuntu-latest / ubuntu-24.04
What problem do you want to solve?
In the workflow .github/workflows/ci.yml with job
testthe strategy.matrix uses the default strategy.fail-fast value oftrueso that any failedmatrixjobs cause the whole higher leveltestjob to be cancelled.This is currently the case in https://github.com/eslint/css/actions/workflows/ci.yml due to eslint/csstree#27.
In general it is more convenient to allow all matrix jobs to run to their own independent completion. This gives a better overview of where failures are occurring. For example, they may affect all configurations, certain Node.js versions or certain operating system only.
What do you think is the correct solution?
In the workflow .github/workflows/ci.yml add
fail-fast: trueto thematrixparameters.Participation
Additional comments
No response