ci: the suites' JUnit results as comments on the pull request #45
No reviewers
Labels
No labels
ansible
bug
ci
dependencies
digest
docker
documentation
duplicate
enhancement
fix
go
good first issue
help wanted
invalid
javascript
major
minor
patch
php
python
question
released
security
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dawid/osmapp!45
Loading…
Reference in a new issue
No description provided.
Delete branch "ci-test-report"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The three suites already wrote JUnit (
junit-python.xml,junit-node.xml,junit-e2e.xml), which nothing read since the move from GitHub. Each now goes to the pull request throughdawid/ci-actions' test-report: a comment per suite (Test (Python),Test (Node),Test (E2E)), edited in place by every run, with the totals and each failure's message..github/workflows/ci.yml, a Heroku deploy, GitHub's annotations and uploaded traces; it now says what.forgejo/workflows/ci.ymldoes (no artifacts: traces are replayed locally).🤖 Generated with Claude Code
Tests of Build, Test and Deploy OSM App / test_python: passed
111 passed, 0 failed, 0 skipped (111 tests, 1.1 s)
Of
488766ff37, the run, updated by every run.Tests of Build, Test and Deploy OSM App / test_javascript: passed
678 passed, 0 failed, 0 skipped (678 tests, 4.1 s)
Of
488766ff37, the run, updated by every run.Tests of Build, Test and Deploy OSM App / test_e2e: passed
150 passed, 0 failed, 0 skipped (150 tests, 577.8 s)
Of
488766ff37, the run, updated by every run.