Error reporting for tests is very unclear

[broonie]

If I copy the example from the documentation:

kci-dev results tests --giturl 'https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git' --branch master --commit d1486dca38afd08ca279ae94eb3a397f10737824

then I get useful output from kci-dev (that's next-20241209). If I try to modify that command line to today's -next 64d12554715ce825d553caea123b7cb89e56237a I get:

$ kci-dev results tests --giturl 'https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git' --branch master --commit 64d12554715ce825d553caea123b7cb89e56237a
json error: Tree checkout not found

This appears to be happening because no tests were run for today, but I'm struggling to tell that based on the diagnostic output provided.

[aliceinwire]

Proabably this should be reported also to dashboard
as the message come from there:
https://github.com/kernelci/dashboard/blob/7573ea2662d892fc6656c5804b260d438b4e05db/dashboard/src/locales/messages/index.ts#L314

[broonie]

Possibly, though there's also the issue that "checkout" is kind of a confusing term for an end user running on their local system but a sensible one in the API - on the local system (especially with being able to specify --git-folder) it might be referring to something on my local system. That might be addressable by specifying that the message comes from the server?

[aliceinwire]

That might be addressable by specifying that the message comes from the server?

sure that could be one option

[padovan]

@aliceinwire @broonie I started with changing the message on the dashboard side kernelci/dashboard#1255

Please take a look.