Skip to content

Conversation

@mkeskells
Copy link
Contributor

@mkeskells mkeskells commented Aug 2, 2025

publish test results

SUMMARY

  • Describe your changes, including rationale and design decisions
    report errors better in junit
    publish junit results in CI

no functional chnages in this PR

there are a coupe of chnages

  • using the junit APIs to gett a better failure message whenthere is an issue, an some code compaction
  • changing the workflow to generate test artifacts, and publish then the the PR results - this makes the viewing of the errors easier. This chnage works in 2 halves, the publish and the render (which is in the post* workflows)
    Unfortunately the post workflows only run in the main branch, so I cand demo then in this PR

Automated Checks

  • I have run ./gradlew test and made sure that my PR does not break any unit test.

@mkeskells mkeskells marked this pull request as draft August 2, 2025 13:06
@mkeskells mkeskells force-pushed the testing-visibility branch 4 times, most recently from 87c1f56 to c91185b Compare August 4, 2025 21:21
@mkeskells mkeskells marked this pull request as ready for review August 4, 2025 21:37
@mkeskells mkeskells force-pushed the testing-visibility branch from c91185b to 555eb67 Compare August 4, 2025 21:42
@lemire lemire merged commit 5489517 into RoaringBitmap:master Aug 5, 2025
7 checks passed
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