kernelci / kernelci/kernelci-pipeline
Stop sending dummy builds to KCIDB
- Dominant language
- Python
- Stars
- 11
- Forks
- 40
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 14
Description
Today we send dummy builds for tests that "doesn't have a build" like kunit. Eg: https://d.kernelci.org/build/maestro%3Adummy_67b474b350b59caecce1abbe_x86_64
I am sure kunit is running against a given kernel on a given config, but the way Maestro is doing it seems to not comply with the current node hierarchy we use. Let have this ticket to investigate this issue.
In the meantime we will amend the Web Dashboard query to not get dummy builds.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how Maestro represents tests without a build and how those results enter KCIDB; the issue provides no file or test entry point. Compare that behavior with the current node hierarchy and the Web Dashboard query, and consider the work complete when valid test results no longer require dummy builds and remain correctly represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100