kernelci / kernelci/kci-dev

Enhancement: Lab and board identifier information in kci-dev --json output

Open
#203 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
10
Forks
11
Avg merge
11d 23h
Merged PRs (30d)
9

Description

kci-dev results boots --giturl 'https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git' --branch master --latest --json
For example throws out the following:
` {
"test_path": "boot",
"hardware": "rk3288-rock2-square",
"compatibles": [
"radxa,rock2-square",
"rockchip,rk3288"
],
"config": "multi_v7_defconfig",
"arch": "arm",
"status": "INCONCLUSIVE (status: MISS)",
"start_time": "2025-07-09T13:46:04.972000Z",
"log": "https://files.kernelci.org/baseline-arm-686e729c34612746bbbb15a4/log.txt.gz",
"id": "maestro:686e729c34612746bbbb15a4",
"dashboard": "https://dashboard.kernelci.org/build/maestro:686e729c34612746bbbb15a4"
}
`
It would be helpful to identify which lab the information came from and possibly if the lab has multiple boards, some sort of board identifier to know if the reported issue is specific to a type of board.

Contributor guide

Open the contributing guide

Research direction

Start with the `kci-dev results boots --giturl ... --latest --json` entry point and trace how each result object is assembled. Identify the available lab and board identifiers, expose them in the JSON output, and verify that the example boot results include the new fields.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.