Goal
Simplify the complete Infection GitHub Actions workflow so LibreSign has one reliable CI execution path for full mutation runs and preserves enough evidence for baseline analysis.
This workflow is for complete mutation runs. It is separate from the normal pull-request change-aware mutation workflow.
Current problem
The current Infection workflow combines mutation testing with a PHP/Nextcloud compatibility matrix.
Mutation testing and compatibility testing answer different questions.
LibreSign already has normal PHPUnit/CI coverage for supported runtime combinations. Repeating the complete mutation suite across a compatibility matrix can multiply an already expensive workload without evidence that each combination provides distinct mutation-testing signal.
Investigation
Before removing the current matrix, verify:
- what compatibility coverage is already provided by normal PHPUnit workflows;
- whether Infection has produced mutation-specific failures on different supported PHP/Nextcloud combinations;
- which PHP and Nextcloud versions should define the canonical full-mutation environment;
- whether more than one full-run combination has a measured reason to remain.
Do not remove compatibility coverage merely to reduce runtime.
Do not retain duplicate mutation runs merely because the matrix already exists.
Required outcome
Provide a complete-run Infection workflow that:
- can be started from GitHub Actions;
- uses the agreed canonical runtime configuration;
- keeps workflow YAML focused on orchestration;
- exposes the effective Infection command/configuration;
- preserves useful logs and machine-readable reports;
- records runtime and environment metadata;
- fails visibly for operational Infection/PHPUnit failures.
The workflow must not introduce an arbitrary blocking mutation-score threshold.
Reporting
Preserve enough information to diagnose:
- generated mutants;
- killed mutants;
- escaped mutants;
- uncovered mutants;
- timeout mutants;
- execution errors;
- MSI and Covered Code MSI;
- total runtime.
When Infection supports a suitable machine-readable report, preserve it as a GitHub Actions artifact.
Parallelism
Use only a worker/thread configuration shown to be safe for LibreSign test isolation.
Do not force --threads=1 permanently only to hide shared-state races.
Done when
Related
Goal
Simplify the complete Infection GitHub Actions workflow so LibreSign has one reliable CI execution path for full mutation runs and preserves enough evidence for baseline analysis.
This workflow is for complete mutation runs. It is separate from the normal pull-request change-aware mutation workflow.
Current problem
The current Infection workflow combines mutation testing with a PHP/Nextcloud compatibility matrix.
Mutation testing and compatibility testing answer different questions.
LibreSign already has normal PHPUnit/CI coverage for supported runtime combinations. Repeating the complete mutation suite across a compatibility matrix can multiply an already expensive workload without evidence that each combination provides distinct mutation-testing signal.
Investigation
Before removing the current matrix, verify:
Do not remove compatibility coverage merely to reduce runtime.
Do not retain duplicate mutation runs merely because the matrix already exists.
Required outcome
Provide a complete-run Infection workflow that:
The workflow must not introduce an arbitrary blocking mutation-score threshold.
Reporting
Preserve enough information to diagnose:
When Infection supports a suitable machine-readable report, preserve it as a GitHub Actions artifact.
Parallelism
Use only a worker/thread configuration shown to be safe for LibreSign test isolation.
Do not force
--threads=1permanently only to hide shared-state races.Done when
Related
infection.json5