Skip to contentSkip to conversation

Testing 4.4.302-cip80-rt46 fails at test:x86_cip_qemu_defconfig_release

DISCUSSION Pavel Machek 2 participants 2 messages Oct 27, 2023 – Oct 28, 2023

lore
Share & tools
lore
#0 lore raw

Hi!

I'm preparing 4.4-cip-rt release, and I'm getting test failure:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1050438468

Has anything changed recently w.r.t. testing? I don't seem to remember test:x86_cip_qemu_defconfig_release variant.

Could someone look at the tests and help me analyze the failure?

Best regards,
Pavel

Signature · 2 lines
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
#1 lore raw

Hello Pavel,

Quoted 11 lines

From: Pavel Machek <[email protected]>
Sent: Friday, October 27, 2023 12:52 PM

Hi!

I'm preparing 4.4-cip-rt release, and I'm getting test failure:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1050438468

Has anything changed recently w.r.t. testing? I don't seem to remember test:x86_cip_qemu_defconfig_release variant.

Nothing relevant has changed recently,
and looking at the GitLab pipeline definition this job shouldn't have been run as it checks for branches containing /^.*-rc$/ in the name (see [0]), which "ci/pavel/linux-test" doesn't. Maybe it's a glitch in the matrix.
Is it happening every time?

[0] https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/blob/master/linux-cip-pipeline.yml?ref_type=heads#L59

On another note, because you're using the "ci/pavel/linux-test" branch, the RT tests aren't being run - do you want them to? You need to push a branch name ending with "-rt" to pick the RT tests up automatically.
e.g. ci/pavel/linux-test-rt
See [1] for the regex it uses.

We did it like this so we didn't have to change the .gitlab-ci.yml file in the RT branches to point to a different pipeline definition compared to the non-RT branches.

[1] https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/-/blob/master/linux-cip-pipeline.yml?ref_type=heads#L54

Quoted 2 lines

Could someone look at the tests and help me analyze the failure?

It failed to log in before a timeout. I'm not sure why.
It looks like it failed to mount the rootfs.
It seems fine on a retry: https://lava.ciplatform.org/scheduler/job/1028621

Kind regards, Chris

Quoted 6 lines

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany