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.

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

Replace pytest-results-action with a custom xml parser script #417

Merged
merged 16 commits into from
Jan 7, 2025

Conversation

andrewmogan
Copy link
Collaborator

Our current nightly integration test workflow uses a pytest-results-action, a barely maintained GitHub action that creates a summary table of pytest results. What's more, we don't even use the main branch of that action, but a fork I made to slightly improve the table formatting for our purposes. Rather than rely on a barely maintained fork of a barely maintained third party action, this PR introduces a python script under scripts/github-ci to achieve a similar result while allowing greater flexibility and removing a third party dependency. Similar to our nightly code check workflow, this script creates a markdown summary file which is then added to GITHUB_STEP_SUMMARY. Sample results are linked below.

Sample v5 results

Sample v4 results

…ated due to the #418 merge.

Merge branch 'develop' into amogan/integtest_markdown_parser
Copy link
Collaborator

@jcfreeman2 jcfreeman2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The output of the integration tests is much easier on the eyes and a lot clearer. A comment and a question:

  1. The merge of PR Extend nightly integration tests to work on candidate or frozen builds #418 into develop resulted in a divergence which I fixed by merging develop into this PRs feature branch and then resolving a couple of conflicts via commit c5f7a72.
  2. It's a nitpick, but in the old method of presentation the number of total tests presented and their breakdown into passes and fails was prevented; would it be hard to bring this back? Something like "62 tests passed, 2 tests failed" at the very bottom of the output.

@andrewmogan
Copy link
Collaborator Author

Added a summary line at the top: https://github.com/DUNE-DAQ/daq-release/actions/runs/12654961917

@jcfreeman2
Copy link
Collaborator

Looks great; approved.

@jcfreeman2 jcfreeman2 merged commit 297ddcb into develop Jan 7, 2025
14 of 15 checks passed
@jcfreeman2 jcfreeman2 deleted the amogan/integtest_markdown_parser branch January 7, 2025 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants