Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define best practice for wiring up mill test runs to github actions #4202

Open
lihaoyi opened this issue Dec 29, 2024 · 1 comment
Open

Define best practice for wiring up mill test runs to github actions #4202

lihaoyi opened this issue Dec 29, 2024 · 1 comment

Comments

@lihaoyi
Copy link
Member

lihaoyi commented Dec 29, 2024 •
edited
Loading

Currently Mill's own build just outputs things to stdout for us to scroll through. Other projects probably do something similar.

We should figure out a better way of integrating the structured test.xml output files into github actions markdown reports, so we can easily see summaries of the test results without scrolling through thousands of lines of logs, and document the setup for others to use
@sake92 sake92 mentioned this issue Dec 31, 2024
Merged
lihaoyi pushed a commit that referenced this issue Jan 1, 2025
@sake92
Add junit report action (#4218)
174c6bb 
Improves #4202 

Example reports: https://github.com/sake92/mill/actions/runs/12563637492

If you click on a failed job on the left, you will see annotations
section on the top.
It shows which tests failed and the reason message.
@lihaoyi
Copy link
Member Author

lihaoyi commented Jan 1, 2025

#4218 helps a lot, remaining improvements would be to try and show stack traces (mikepenz/action-junit-report#1278) and task names in the annotations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lihaoyi