kernelci / kernelci/kci-bisect
Define building block components and interfaces
Open
Nobody has claimed this yet.
architecture
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Meta-issue: work out what the actual pieces are and how they talk to
each other.
Starting list from docs/architecture.md:
- Bisection loop / orchestrator
- Commit selector (midpoint or n-bisect)
- Build step (TuxMake, Maestro, custom)
- Build cache
- Test step (TuxRun/QEMU, LAVA, custom)
- Result parser (logspec for error signatures)
- Reporting (email, recipients, Lore lookup)
- Verification (revert + retest)
Goal for the follow-up meeting: look at the contributed scripts and
agree on what to build first and what the interfaces look like.
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
Start with docs/architecture.md and review the contributed scripts referenced in the issue. Map the listed components and their interactions, then use the follow-up meeting to agree on what to build first and what each interface should be; done means that initial scope and interface decisions are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100