Repository navigation
Conversation
|
Thanks for reworking this so quickly, @ai94iq! Dropping the output.xml parser, the listener and the in-place What already covers result readingSince content 3.0.0, these teach reading results with
A separate skill that triggers after every run would also use part of the skill-listing budget (about 8,000 characters in Claude Code). Where your grouping idea could go1. Upstream in robotcode. Grouping failures that differ only by ids, hosts or timestamps would help every robotcode user, not just agents. An issue at https://github.com/robotcodedev/robotcode could look like this: Title: results: group failed tests by normalised message
`robotcode results show --failed` lists each failure on its own. In large runs many failures
share one cause and differ only by ids, hosts or timestamps:
Order 4711 not found (GET https://api-1.example.com/orders/4711)
Order 4712 not found (GET https://api-2.example.com/orders/4712)
Proposal: `robotcode results show --failed --group-by message`, which replaces numbers, UUIDs,
hosts and timestamps with placeholders and prints each group once with its count and test names:
2x Order {id} not found (GET {host}/orders/{id})
Orders.Get Order By Id, Orders.Get Archived OrderYour earlier digest code already shows the normalisation rules, so a PR to robotcode could be within reach too. 2. Here, once robotcode has it. The manual version is already on its way: your #14 adds fingerprints (ids replaced, hosts and timestamps dropped) to When you update the branch, please base it on AI assistanceWe published AI_POLICY.md after you opened this PR, so you couldn't have known about it. It now applies to all open PRs, including this one. When you update, could you add the "AI assistance" section from the current PR template to the description (one line is enough, or "none" if no tool was involved)? Thanks again for taking the feedback on board so well, and I'm looking forward to where this goes! 🙂 PS: I merged #13, #14, #15 and #16 today. I made a few small adjustments myself so they could go in right away; each PR's last comment lists them. Thanks for those! 🎉 |
|
Hi @ai94iq, a short update: 5.0.0 is out and removed the Everything else from my last comment stays the same: we keep this PR open while the grouping idea goes to robotcode, so a link to that issue here would be great. Thanks! 🙂 |
Rebased on main without the rf-test-quality change.
d36753c to
41847c9
Compare
|
Thanks @manykarim. Rebased on main without #11, regenerated with |
Two harness tests list rf-core's staged skills by name; the new skill is now one of them.
What this changes
Adds the
rf-run-digestskill to rf-core: reading a finished run withrobotcode resultsand grouping failures by cause. Rebased onmainwithout #11. Parked until robotcode has a grouping command: robotcodedev/robotcode#697.AI assistance
Claude Code (Claude Opus) made the edits and ran the checks. I reviewed the diff and the check output, and I have the right to submit it.
Before you open it
robotcode; gaps are reported upstream.python scripts/build-agent-variants.pyandpython scripts/build-catalog.py.For the reviewer
Skill metadata follows 5.0.0 (no
metadata.version; author ai94iq). Installer test counts and REQUIRED_ROWS include rf-run-digest. Maintainers per catalog.yaml: @manykarim.Local checks:
pytest tests --ignore=tests/evalgreen on the installer, description, structure and command suites; catalogue, governance, skill validation, plugin references and docs voice pass.