From: Pavel Machek <pavel@denx.de>
To: Chris.Paterson2@renesas.com, cip-dev@lists.cip-project.org
Subject: kernelci results for v4.4.302-cip68
Date: Wed, 16 Feb 2022 11:19:37 +0100 [thread overview]
Message-ID: <20220216101937.GB30022@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
Hi!
I'm trying to understand how to work with kernelci. I thought I'd
start with understanding 4.4.302 results, so I went to examine some.
a) qemu failing
I got to
https://storage.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip68/arm64/defconfig+arm64-chromebook/gcc-10/lab-baylibre/baseline-qemu_arm64-virt-gicv2.html
171 22:36:34.473034 qemu-system-aarch64: Property '.mte' not found
175 22:36:34.476041 boot-image-retry failed: 1 of 1
attempts. 'Connection closed'
177 22:36:34.476572 end: 2 boot-image-retry (duration 00:00:01)
[common]
190 22:36:34.590951 InfrastructureError: The Infrastructure is
not working correctly. Please report this error to LAVA admins.
This one does not look like kernel problem.
b) fuloong2e
Newer builds fail (v4.4.302-cip68) while older ones did not
(v4.4.266-cip56), example board is fuloong2e. Error is:
cc1: error: ‘-mloongson-mmi’ must be used with ‘-mhard-float’
cc1: error: ‘-mloongson-mmi’ must be used with ‘-mhard-float’
This well might be build infrastructure problem, and I don't think we
care too much. What should be done there?
c) We have ton of "test execution failed", such as
https://linux.kernelci.org/test/case/id/61e26bcc0c981e7374ef6770/
. Unfortunately clicking on "job log", txt or html, gives me 404 page.
Can you take a look at
https://linux.kernelci.org/test/job/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip68/
and point me to any kernel problems I should debug shown there?
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
reply other threads:[~2022-02-16 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220216101937.GB30022@amd \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
/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