Skip to content

Can't run txtar with coverage (#688) #2022

Can't run txtar with coverage (#688)

Can't run txtar with coverage (#688) #2022

Triggered via push October 19, 2024 18:47
Status Success
Total duration 4m 25s
Artifacts 1

ci.yml

on: push
Matrix: build-and-test
Test in Docker
2m 6s
Test in Docker
Test parser against vast amount of Markdowns
28s
Test parser against vast amount of Markdowns
Matrix: lint
SonarCloud Analysis
12s
SonarCloud Analysis
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test parser against vast amount of Markdowns
The following actions use a deprecated Node.js version and will be forced to run on node20: stateful/runme-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build and test with Go 1.22 on ubuntu-latest
The following actions use a deprecated Node.js version and will be forced to run on node20: stateful/runme-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Lint with Go 1.22
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test in Docker
The following actions use a deprecated Node.js version and will be forced to run on node20: stateful/runme-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
coverage Expired
2.11 MB