KernelCI, gitlab testing notes

[Pavel Machek <pavel@denx.de>]

[-- Attachment #1: Type: text/plain, Size: 2696 bytes --]

Hi!

* 4.4 kernelci warnings

https://linux.kernelci.org/build/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip70-98-g7f7838c92740f/

Thanks for pointer. This looks good. Most of warnings are
"net/ipv4/inet_hashtables.c:608:68: warning: suggest parentheses
around ‘+’ in operand of ‘&’ [-Wparentheses]" which is my fault and on
my TODO list.

* SMC QEMU x86-64

https://storage.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip70-98-g7f7838c92740f/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.html

Ok, I'll need to know more about the config. Is it possible that qemu
runs paravirtualized -- KVM?

If yes, we are basically testing whatever hardware it happens to run
on. Not good.

If no... the "soft" cpu it runs on does not have those bugs.

* Understanding gitlab results

+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/3184699360

Ok, so what should I be looking at?

-----------------------------------
374All submitted tests were successful
375-----------------------------------
376------------------------------
377Job Summary
378------------------------------
379Job #763143 Finished. Job health: Complete. URL: https://lava.ciplatform.org/scheduler/job/763143
380Job #763147 Finished. Job health: Complete. URL: https://lava.ciplatform.org/scheduler/job/763147
382

I have see. "Job health: incomplete" and that indicated problems. I
see "All submitted tests were successful". I guess that's ok.

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/3141003858

Now that's pretty evil:

* 0_spectre-meltdown-checker-test.CVE-2018-12126 [fail]
266* 0_spectre-meltdown-checker-test.CVE-2018-3646 [pass]
...
288-----------------------------------
289All submitted tests were successful
290-----------------------------------
291

First, make it stand out visually. [pass] => [ok] and [fail] =>
[FAILURE] or something like that.

Second, saying all tests were successful (line 289) when there's
failure is ... confusing.

* LTP failures

I'm not sure where we run this or how. Anyway.

https://lava.ciplatform.org/scheduler/job/763461

I picked up one failure randomly, and that's config failure, not
kernel failure: utimensat01 1 TBROK: can't read /etc/sudoers

Not sure what is going there: quotactl01. Do we have quotas enabled?
syslog01 and friends is also failing. Is syslog configured correctly?

I guess best way would be to run ltp on 4.4-mainline, 4.4.302, 4.4-cip
and compare the results.

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]