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

[nmenon]

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.

[padovan]

We didn't had time to hook up lab information properly in KernelCI yet. In your case, if you are looking at TI lab, you have to filter by --origin ti. That would be your "lab", but conceptually a KCIDB origin in KernelCI.

As for identifying boards. That is fully out of scope today in KernelCI. For the lava labs we use the device-type information and defer to LAVA, the scheduling of the job on one of their devices.

That being said, we would be happy to discuss and implement possible solutions for these things if TI wants to step forward and contribute to core KernelCI components and send patches. :)

[nmenon]

in my case, I am looking for more than TI Labs - I want to see all labs reporting ti SoC status..

for example, my scripts report:
{'test_path': 'boot', 'hardware': 'am57xx-beagle-x15', 'compatibles': ['ti,am572x-beagle-x15', 'ti,am5728', 'ti,dra742', 'ti,dra74', 'ti,dra7'], 'config': 'multi_v7_defconfig', 'arch': 'arm', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T09:40:04.126000Z', 'log': None, 'id': 'maestro:686f8a7434612746bbbdf8aa', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8a7434612746bbbdf8aa'} Ignoring empty log: {'test_path': 'boot', 'hardware': 'beaglebone-black', 'compatibles': ['ti,am335x-bone-black', 'ti,am335x-bone', 'ti,am33xx'], 'config': 'multi_v7_defconfig', 'arch': 'arm', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T09:40:10.529000Z', 'log': None, 'id': 'maestro:686f8a7a34612746bbbdf8be', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8a7a34612746bbbdf8be'} Ignoring empty log: {'test_path': 'boot', 'hardware': 'da850-lcdk', 'compatibles': ['ti,da850-lcdk', 'ti,da850'], 'config': 'multi_v7_defconfig', 'arch': 'arm', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T09:40:12.404000Z', 'log': None, 'id': 'maestro:686f8a7c34612746bbbdf9ac', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8a7c34612746bbbdf9ac'} Ignoring empty log: {'test_path': 'boot', 'hardware': 'beagle-xm', 'compatibles': ['ti,omap3-beagle-xm', 'ti,omap3630', 'ti,omap3'], 'config': 'multi_v7_defconfig', 'arch': 'arm', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T09:40:08.791000Z', 'log': None, 'id': 'maestro:686f8a7834612746bbbdf8b7', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8a7834612746bbbdf8b7'} Ignoring empty log: {'test_path': 'boot', 'hardware': 'k3-j721e-beagleboneai64', 'compatibles': ['beagle,j721e-beagleboneai64', 'ti,j721e'], 'config': 'defconfig+lab-setup+kselftest', 'arch': 'arm64', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T10:02:18.491000Z', 'log': None, 'id': 'maestro:686f8faa34612746bbbe125a', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8faa34612746bbbe125a'} Ignoring empty log: {'test_path': 'boot', 'hardware': 'k3-j721e-sk', 'compatibles': ['ti,j721e-sk', 'ti,j721e'], 'config': 'defconfig+lab-setup+kselftest', 'arch': 'arm64', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-10T10:02:17.097000Z', 'log': None, 'id': 'maestro:686f8fa934612746bbbe1257', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:686f8fa934612746bbbe1257'}

I have no idea whose lab this came from. lab-baylibre or lab-broonie or someone else.. same applies if I were to see a fault..

[aliceinwire]

in my case, I am looking for more than TI Labs - I want to see all labs reporting ti SoC status..

excluding all the qemu ? only SoC?

having a filter like --exclude-hardware=qemu would help?

[padovan]

in my case, I am looking for more than TI Labs - I want to see all labs reporting ti SoC status..

excluding all the qemu ? only SoC?

having a filter like --exclude-hardware=qemu would help?

It seems more like, including only the TI hardware. A key limitation is that we don't have a structured way to store hw information. All we have today is hw platform and compatibles. We are missing things like vendor, mach, component info(CPU, memory, NIC, etc). This has to be built yet.

In the meantime, one can see all hw through:
kci-dev results hardware list

and then use that to populate --filter https://kci.dev/results/#filter

I'll see if I can do something quick for lab in the meantime. We kind have that info in a misc(non-oficial) KCIDB field.

[padovan]

I was able to hook it for the boot and test commands. Not boots and tests mind you. #207

When using --json it will spit the runtime field where you can read the lab info. Right now we offer no guarantee that this field won`t change in the future. :)

Bringing it to boots and tests is a bit more complicated and will probably affect the performance of the API execution because the lab info in inside a json stored in the misc field of our SQL!

[nmenon]

Thanks, @padovan. I can work with this. However, having a board-specific ID will help us narrow down logs to a specific board to understand patterns of random failures (the trigger was a networking issue that randomly occurs in the upstream, which I have been trying to narrow down). That said, this is definitely a step in the right direction..

$ kci-dev results boot --id maestro:6871d16e34612746bbc023cc --json

{'test_path': 'boot', 'hardware': 'dell-latitude-5300-8145U-arcada', 'compatibles': None, 'config': 'defconfig+kcidebug+x86-board', 'arch': 'i386', 'status': 'INCONCLUSIVE (status: MISS)', 'start_time': '2025-07-12T03:07:26.140000Z', 'log': 'https://files.kernelci.org/baseline-x86-kcidebug-intel-6871d16e34612746bbc023cc/log.txt.gz', 'id': 'maestro:6871d16e34612746bbc023cc', 'dashboard': 'https://dashboard.kernelci.org/build/maestro:6871d16e34612746bbc023cc', 'runtime': 'lava-collabora'}