kernelci / kernelci/kernelci-pipeline
Mandatory fields are not available at moment of node generation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
As result of https://github.com/kernelci/kernelci-pipeline/pull/392 we exposed issue, that some of fields might be unavailable at moment when we are generating node, such as:
arch, defconfig, compiler, platform, runtime
We need to think well how and when we define this fields. In some cases they can be just moved at moment of node creation, but in some they might need some "N/A" value when they are unassigned yet.
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
Review pull request #392 and trace the node-generation flow to determine when arch, defconfig, compiler, platform, and runtime become available. Define the required timing or N/A behavior for unassigned fields, then verify that node generation handles each case consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100