All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: spbnick@gmail.com, sachinp@linux.ibm.com
Cc: misbahanjumn@ibm.com,
	"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: Contributing Linux on Power test results to KCIDB
Date: Wed, 22 Mar 2023 14:07:40 +0100	[thread overview]
Message-ID: <6192485a-0229-7469-0c2d-856cdea35fbe@collabora.com> (raw)
In-Reply-To: <aaaa8f94-d901-500f-338d-a39ea8e350eb@gmail.com>

+kernelci@lists.linux.dev

Please use the new list, kernelci@groups.io is now closed.

Guillaume

On 21/03/2023 20:10, Nikolai Kondrashov wrote:
> Hello Sachin,
> 
> We would love to have your data in KCIDB!
> 
> You can start with reading our Submitter Guide:
> 
> https://kernelci.org/docs/kcidb/submitter_guide/
> 
> Then decide and tell us what the "origin" of your CI system should be, so that we could identify it in the database, dashboards, and notifications.
> 
> After that I'll send you credentials with permissions to submit to our "playground" database, so that you could experiment and build up your data and submission system iteratively and interactively. Once that is done, we would give you permissions to submit to our "production" database.
> 
> Don't hesitate to send any question you might have to this maillist, or to our #kernelci IRC channel on libera.chat. If you need more help, we could arrange a video call as well.
> 
> Welcome!
> Nick
> 
> On 3/21/23 17:57, Sachin Sant wrote:
>> Hello List,
>>
>> I am part of Linux on Power team at IBM. Me and my team has developed
>> an automated framework to test various Linux kernel git based repositories
>> on IBM Power servers using avocado [1] based automated tests.
>>
>> These regression and functional tests are executed against
>> - mainline
>> - linux-next
>> - linuxppc tree [2]
>>
>> I am interested in contributing the results (boot and test) to KCIDB project.
>> Let me know how can I get started on this.
>>
>> Thanks
>> - Sachin
>>
>> [1] https://github.com/avocado-framework-tests/avocado-misc-tests
>> [2] https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
>>
>>
>>
>>
>>
>>
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#1656): https://groups.io/g/kernelci/message/1656
> Mute This Topic: https://groups.io/mt/97759547/924702
> Group Owner: kernelci+owner@groups.io
> Unsubscribe: https://groups.io/g/kernelci/leave/2088106/924702/1865905899/xyzzy [guillaume.tucker@collabora.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 
> 


       reply	other threads:[~2023-03-22 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26F2B8E1-8A69-42E9-B3DF-A7E7E847756E@linux.ibm.com>
     [not found] ` <aaaa8f94-d901-500f-338d-a39ea8e350eb@gmail.com>
2023-03-22 13:07   ` Guillaume Tucker [this message]
2023-03-24  8:30     ` Contributing Linux on Power test results to KCIDB Sachin Sant
2023-03-24  8:24   ` Sachin Sant
2023-03-24  9:54     ` Nikolai Kondrashov
2023-04-03  9:43   ` Sachin Sant
2023-04-03 10:03     ` Nikolai Kondrashov

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=6192485a-0229-7469-0c2d-856cdea35fbe@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=misbahanjumn@ibm.com \
    --cc=sachinp@linux.ibm.com \
    --cc=spbnick@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.