public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] CI: Protect Debian Ports targets by KFAIL
Date: Mon, 31 Jan 2022 11:31:33 +0100	[thread overview]
Message-ID: <af2fd323-cd04-6f17-9e87-c433bbb2ce5f@siemens.com> (raw)
In-Reply-To: <caa7596d-ed34-33f8-9411-5c7352997bc3@ilbers.de>

On 31.01.22 10:45, Anton Mikanovich wrote:
> Upstream was broken few days ago, so we need to apply hotfix ASAP before 
> release.
> Will also apply this today if no objections.
> 

sid can only be KFAIL. If you want a reliable test for the risc-v 
targets, you would need to pin to a archived repo revision. But then the 
downloading from snapshot.debian.org will not work reliably...

Jan

> 31.01.2022 12:43, Anton Mikanovich wrote:
>> Debian Ports provides unofficial architectures support which not always
>> stable enough.
>> Currently few sifive-fu540-sid-ports recipes fail with:
>>
>> opensbi-0.9/lib/sbi/sbi_tlb.c: Assembler messages:
>> opensbi-0.9/lib/sbi/sbi_tlb.c:175: Error: unrecognized opcode `fence.i'
>> ...
>> ../arch/riscv/include/asm/timex.h: Assembler messages:
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a5,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a1,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a1,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> t4,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a5,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a5,0xc01'
>> ../arch/riscv/include/asm/timex.h:15: Error: unrecognized opcode `csrr 
>> a2,0xc01'
>>
>> To not block other targets cover both sid-ports targets with KFAIL.
>>
>> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>> ---
>>   testsuite/build_test/build_test.py | 13 +++++++++++--
>>   1 file changed, 11 insertions(+), 2 deletions(-)
>>
>> diff --git a/testsuite/build_test/build_test.py 
>> b/testsuite/build_test/build_test.py
>> index 683aa55d..16f6d0a3 100644
>> --- a/testsuite/build_test/build_test.py
>> +++ b/testsuite/build_test/build_test.py
>> @@ -124,8 +124,6 @@ class NoCrossTest(CIBaseTest):
>>               'mc:qemuamd64-bullseye:isar-initramfs',
>>               'mc:qemumipsel-buster:isar-image-base',
>>               'mc:qemumipsel-bullseye:isar-image-base',
>> -            'mc:qemuriscv64-sid-ports:isar-image-base',
>> -            'mc:sifive-fu540-sid-ports:isar-image-base',
>>               'mc:imx6-sabrelite-bullseye:isar-image-ubi',
>>               'mc:phyboard-mira-bullseye:isar-image-ubi',
>>               'mc:rpi-arm-bullseye:isar-image-base',
>> @@ -160,6 +158,17 @@ class NoCrossTest(CIBaseTest):
>>           except:
>>               self.cancel('KFAIL')
>> +    def test_nocross_sidports(self):
>> +        targets = [
>> +            'mc:qemuriscv64-sid-ports:isar-image-base',
>> +            'mc:sifive-fu540-sid-ports:isar-image-base'
>> +                  ]
>> +
>> +        try:
>> +            self.perform_build_test(targets, 0, None)
>> +        except:
>> +            self.cancel('KFAIL')
>> +
>>   class RebuildTest(CIBaseTest):
>>       """
> 

-- 
Siemens AG, Technology
Competence Center Embedded Linux

  reply	other threads:[~2022-01-31 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31  9:43 Anton Mikanovich
2022-01-31  9:45 ` Anton Mikanovich
2022-01-31 10:31   ` Jan Kiszka [this message]
2022-01-31 15:52 ` Anton Mikanovich

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=af2fd323-cd04-6f17-9e87-c433bbb2ce5f@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --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