From: Nikolai Kondrashov <Nikolai.Kondrashov@redhat.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: kernelci@lists.linux.dev
Subject: Re: Kcidb access request
Date: Tue, 27 Aug 2024 12:42:19 +0300 [thread overview]
Message-ID: <85c76e9d-0c60-4771-9ae6-12ea511c495e@redhat.com> (raw)
In-Reply-To: <4fqub2pii3v6lwasvuzbyyviqgv76aycwhbfcgvxbgjk5h6qdc@25jqm7ubkqyg>
Hi Bjorn,
On 8/26/24 7:01 PM, Bjorn Andersson wrote:
> On Thu, Aug 08, 2024 at 08:56:12PM GMT, Nikolai Kondrashov wrote:
>> Hi Bjorn,
>> However, we don't have APIs, just the direct access to PostgreSQL, which keeps
>> six months of data. See the attached (abbreviated) schema dump. It largely
>> mirrors the JSON I/O schema, which you can see here:
>>
>> https://github.com/kernelci/kcidb-io/blob/main/kcidb_io/schema/v04_03.py
>>
>
> The guide talks about PubSub interface, perhaps I'm misunderstanding
> this portion?
That Pub/Sub interface is a Google API for sending your testing results to
KCIDB. It doesn't allow querying data.
> No real concern with the direct SQL interface.
Great!
>> Note, that at the moment we have no way to query for "Qualcomm boards", but we
>> have a schema change proposal being discussed to address that.
>>
>
> How do you associate device-specific tests (or any test that pass/fail
> due to device-specific regressions) with a particular device then?
Last week we have deployed support for submitting the `compatible` values from
the top of the device tree of the machine executing a test, as part of test
environment's information. Here's the I/O JSON schema for that:
https://github.com/kernelci/kcidb-io/blob/40f6d20f4e76d8d2b7288390003082f77d0aabb2/kcidb_io/schema/v04_04.py#L577-L602
In the database that is stored in a string array column. We're still
researching how to best query it and which indexes we would need, so a query
like "give me all tests which executed on Quallcomm boards (`qcom`?)" might be
very slow.
Here's a sample of vendors we're getting in the test results in our
"playground" database (from Maestro only so far), on our WIP dashboards:
https://fresh2-kcidb-grafana-m6io3uhhiq-uc.a.run.app/goto/R9b0F5qIg?orgId=1
And no, we don't have the "vendor" dashboard yet :D
> That would be great, and would allow me to make an attempt to tie this
> into my local dashboard...
Great! Could you give me a Google account email, so I could give it access to
the server?
Nick
prev parent reply other threads:[~2024-08-27 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 15:49 Kcidb access request Bjorn Andersson
2024-08-08 17:56 ` Nikolai Kondrashov
2024-08-09 9:54 ` Gustavo Padovan
2024-08-26 16:01 ` Bjorn Andersson
2024-08-27 9:42 ` Nikolai Kondrashov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85c76e9d-0c60-4771-9ae6-12ea511c495e@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=andersson@kernel.org \
--cc=kernelci@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox