From: Helen Koike <helen.koike@collabora.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>,
Gustavo Padovan <gus@collabora.com>
Cc: kernelci@lists.linux.dev, lgoncalv@redhat.com
Subject: Re: Kernelci Job Start Delays
Date: Fri, 10 May 2024 10:56:33 -0300 [thread overview]
Message-ID: <1dda36fe-4af4-4c57-b5ba-19e9e67ea3c3@collabora.com> (raw)
In-Reply-To: <1ed9e9d7-d927-4277-9399-16ab952e6ea2@canonical.com>
Hi Joseph,
On 03/05/2024 15:17, Joseph Salisbury wrote:
> Hi Gustavo,
>
> I just uploaded a new version:
> https://lkml.org/lkml/2024/5/3/811
>
> Is there something I need to do initiate the transition to your new system?
We need to first enable build tests on your tree.
You can follow this example:
https://github.com/kernelci/kernelci-pipeline/pull/502
Basically you need to add your tree under `trees:`, so kernelci knows
which trees to monitor. You need to add a `kbuild-...` job under `jobs:`
and an entry under `platforms:` so kernelci knows where to run.
Let me know if you have any questions regarding that.
Thanks
Helen
>
> Thanks,
>
> Joe
>
>
> On 4/29/24 17:09, Gustavo Padovan wrote:
>> Hi Joseph,
>>
>> Just following up on this to check if you want to initiate the
>> transition of rt tests to our new system. Let us know.
>>
>> Regards,
>>
>> Gustavo
>>
>> On 4/12/24 11:50, Gustavo Padovan wrote:
>>> Hi Joseph,
>>>
>>> I am glad that you reached out. It seems you are pointing out yet
>>> another aging sign of our legacy system. For broad context on that,
>>> check our recent blog post[1].
>>>
>>> The best way of solving your issues would be to move your testing to
>>> the new system. The best plan for the legacy system right now is to
>>> shut it down in the coming months. As we said in the blog post, we
>>> are starting small in number of tests and scaling it step by step,
>>> but always with community engagement to evaluate the results. If you
>>> want to come on board with the rt testing, we would be happy to start
>>> a plan to make that happen.
>>>
>>> Let me know if that is an avenue you would like to explore. If yes,
>>> I'd be interested in knowing which tests you are running.
>>>
>>> Best,
>>>
>>> - Gus
>>>
>>> [1] https://kernelci.org/blog/posts/2024/strategic-updates/
>>>
>>
>
>
prev parent reply other threads:[~2024-05-10 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 15:30 Kernelci Job Start Delays Joseph Salisbury
2024-04-12 15:50 ` Gustavo Padovan
2024-04-29 21:09 ` Gustavo Padovan
2024-04-29 21:11 ` Joseph Salisbury
2024-05-03 18:17 ` Joseph Salisbury
2024-05-10 13:56 ` Helen Koike [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=1dda36fe-4af4-4c57-b5ba-19e9e67ea3c3@collabora.com \
--to=helen.koike@collabora.com \
--cc=gus@collabora.com \
--cc=joseph.salisbury@canonical.com \
--cc=kernelci@lists.linux.dev \
--cc=lgoncalv@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).