From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: kernelci@groups.io, cristian.marussi@arm.com
Cc: broonie@kernel.org, basil.eljuse@arm.com
Subject: Re: Contributing ARM tests results to KCIDB
Date: Thu, 17 Sep 2020 16:52:30 +0300 [thread overview]
Message-ID: <a46c273f-cc69-6748-d74f-02f5034be999@redhat.com> (raw)
In-Reply-To: <20200917125044.GA29636@e119603-lin.cambridge.arm.com>
Hi Christian,
On 9/17/20 3:50 PM, Cristian Marussi wrote:
> Hi Nikolai,
>
> I work at ARM in the Kernel team and, in short, we'd like certainly to
> contribute our internal Kernel test results to KCIDB.
Wonderful!
> After having attended your LPC2020 TestMC and KernelCI/BoF, I've now cooked
> up some KCIDB JSON test report (seemingly valid against your KCIDB v3 schema)
> and I'd like to start experimenting with kci-submit (on non-production
> instances), so as to assess how to fit our results into your schema and maybe
> contribute with some new KCIDB requirements if strictly needed.
Great, this is exactly what we need, welcome aboard :)
Please don't hesitate to reach out on kernelci@groups.io or on #kernelci on
freenode.net, if you have any questions, problems, or requirements.
> Is it possible to get some valid credentials and a playground instance to
> point at ?
Absolutely, I created credentials for you and sent them in a separate message.
You can use origin "arm" for the start, unless you have multiple CI systems
and want to differentiate them somehow in your reports.
Nick
On 9/17/20 3:50 PM, Cristian Marussi wrote:
> Hi Nikolai,
>
> I work at ARM in the Kernel team and, in short, we'd like certainly to
> contribute our internal Kernel test results to KCIDB.
>
> After having attended your LPC2020 TestMC and KernelCI/BoF, I've now cooked
> up some KCIDB JSON test report (seemingly valid against your KCIDB v3 schema)
> and I'd like to start experimenting with kci-submit (on non-production
> instances), so as to assess how to fit our results into your schema and maybe
> contribute with some new KCIDB requirements if strictly needed.
>
> Is it possible to get some valid credentials and a playground instance to
> point at ?
>
> Thanks
>
> Regards
>
> Cristian
>
>
>
>
>
next prev parent reply other threads:[~2020-09-17 13:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 12:50 Contributing ARM tests results to KCIDB cristian.marussi
2020-09-17 13:52 ` Nikolai Kondrashov [this message]
2020-09-17 16:22 ` Cristian Marussi
2020-09-17 17:26 ` Nikolai Kondrashov
2020-09-18 15:21 ` Cristian Marussi
2020-09-18 15:30 ` Nikolai Kondrashov
2020-09-18 15:53 ` Nikolai Kondrashov
2020-09-18 16:42 ` Cristian Marussi
2020-09-18 16:57 ` Nikolai Kondrashov
2020-11-05 18:46 ` Cristian Marussi
2020-11-06 10:35 ` Nikolai Kondrashov
2020-12-02 8:05 ` Nikolai Kondrashov
2020-12-02 9:23 ` Cristian Marussi
2020-12-02 10:16 ` Nikolai Kondrashov
2020-12-02 12:01 ` Cristian Marussi
2020-12-02 13:38 ` Nikolai Kondrashov
2020-12-10 17:23 ` Cristian Marussi
2020-12-10 18:17 ` Nikolai Kondrashov
2020-12-10 20:19 ` Cristian Marussi
2020-12-14 10:23 ` Nikolai Kondrashov
2021-03-15 9:00 ` Nikolai Kondrashov
2021-03-17 19:07 ` Cristian Marussi
2020-09-18 16:06 ` Cristian Marussi
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=a46c273f-cc69-6748-d74f-02f5034be999@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=basil.eljuse@arm.com \
--cc=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=kernelci@groups.io \
/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