Skip to content

explicitly set qlty coverage format #169

explicitly set qlty coverage format

explicitly set qlty coverage format #169

Triggered via push August 2, 2025 14:29
Status Success
Total duration 1m 21s
Artifacts

ci.yml

on: push
Matrix: run-tests
slack-notify
3s
slack-notify
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 2 notices
run-tests (ubuntu-latest, 8.1)
qlty 0.558.0 linux-x64 (b0a3def 2025-07-27) 2025-08-02T14:30:22.099498Z https://qlty.sh/d/coverage SETTINGS cwd: /home/runner/work/mo4-coding-standard/mo4-coding-standard METADATA CI: GitHub Commit: c55cb457fd338cce9f429d14e90a51b7a1285e38 Branch: 10.x-stable Build ID: 16694595805:1 Commit Time: 2025-08-02 14:29:23 UTC COVERAGE FILES: 1 Coverage File Format Size coverage.xml cobertura 37.18 KiB ERROR > Failed to parse XML text > > Caused by: > custom: missing field `packages`
run-tests (ubuntu-latest, 8.1)
Error uploading coverage. Output from the Qlty CLI follows:
run-tests (ubuntu-latest, 8.1)
Unexpected input(s) 'format', valid inputs are ['token', 'coverage-token', 'oidc', 'files', 'add-prefix', 'strip-prefix', 'tag', 'verbose', 'skip-errors', 'skip-missing-files', 'total-parts-count']
run-tests (windows-latest, 8.1)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
run-tests (windows-latest, 8.1, --prefer-lowest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677