oxidecomputer / oxidecomputer/buildomat
text search of historical job logs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When running into a new CI failure, when I suspect the failure to be unrelated to the change being tested, I often want to know "have we hit this particular failure on main before?" or "have we ever hit this particular failure before"? I usually search GitHub issues first for some uncommon part of the failure message. That helps sometimes. It would be neat if I could similarly search past buildomat job logs, too. A regex seems handy but really I'm usually just picking an exact string match (filename of a panic, or a panic message, etc).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating how buildomat stores and exposes historical job logs, then clarify whether exact-string and regex search are both required and what log history must be searchable. Done should provide a defined way to find matching failures in past logs, with behavior agreed for both search modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100