public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] CI: Remove KFAIL for Ubuntu
Date: Tue, 18 Jul 2023 16:50:58 +0300	[thread overview]
Message-ID: <761c23cb-6175-821c-fb17-80a2862a1f19@ilbers.de> (raw)
In-Reply-To: <20230718145609.341d5ac3@md1za8fc.ad001.siemens.net>

18/07/2023 15:56, Henning Schild wrote:
> Am Tue, 18 Jul 2023 14:36:42 +0300
> schrieb Anton Mikanovich <amikan@ilbers.de>:
>
>> There were no KFAILs for Ubuntu for a long time already, so it looks
>> stable enough to remove CI protection from it.
>>
>> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>> ---
>>   testsuite/citest.py | 14 ++------------
>>   1 file changed, 2 insertions(+), 12 deletions(-)
>>
>> diff --git a/testsuite/citest.py b/testsuite/citest.py
>> index 0d30b883..c706abe0 100755
>> --- a/testsuite/citest.py
>> +++ b/testsuite/citest.py
>> @@ -129,7 +129,8 @@ class CrossTest(CIBaseTest):
>>               'mc:de0-nano-soc-bullseye:isar-image-base',
>>               'mc:stm32mp15x-bullseye:isar-image-base',
>>               'mc:qemuarm-bookworm:isar-image-ci',
>> -            'mc:qemuarm64-bookworm:isar-image-ci'
>> +            'mc:qemuarm64-bookworm:isar-image-ci',
>> +            'mc:qemuarm64-focal:isar-image-base'
> same here, consider trainling commas in these arrays ... maybe a patch
> on top to add them everywhere
>
> Henning

Agree, will prepare a patch on top of all CI-related stuff.


  reply	other threads:[~2023-07-18 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 11:36 Anton Mikanovich
2023-07-18 12:07 ` Jan Kiszka
2023-07-18 12:56 ` Henning Schild
2023-07-18 13:50   ` Anton Mikanovich [this message]
2023-08-02  4:07 ` Uladzimir Bely

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=761c23cb-6175-821c-fb17-80a2862a1f19@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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