Repository navigation
Show the test status per OS and memory model in the README - #77
Merged
Merged
Conversation
The badge of a workflow can only say how the whole of it went, so the test jobs now record a result for each memory model and a final job publishes them to the `badges` branch as shields.io endpoint files. The README shows them as a table, with the overall Tests badge above it. Only a push to main updates the badges: a manual run may use an older compiler. A model with no result never reached its tests and shows red. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Until now a problem only showed up after the merge. The badges still come from pushes to main alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Testsbadge, and a table with one badge per OS (Windows, Ubuntu 24.04) and memory model (gc,rc,none,own). Each badge covers release and debug, compiled and under the JIT.tests.yml: the test jobs record a result per model and upload it, even when a model fails. A newbadgesjob turns the results into 8 shields.io endpoint files and force-pushes them to abadgesbranch, which holds only those files in a single commit.tests.ymltrigger: the tests now also run on pull requests intomain, so problems show up before a merge. Thebadgesjob still runs only for pushes tomain.Why
GitHub's workflow badge only reports the workflow as a whole, so it can't show which OS or memory model failed.
Reviewer notes
badgesbranch on the first run. The new job hascontents: writefor this; it uses the defaultGITHUB_TOKENand needs no secrets.main, because a manual run may use an older compiler.Testing
🤖 Generated with Claude Code