# LKFT's email checklist

This is a short summary of what have to be done before fire out an email.

## checklist before sending out emails.

Check if anything have been upgraded since last build, like:
[ ] Toolchain
[ ] Base file system
[ ] Test suite overlay
[ ] QEMU

NOTE: if any changed, rebuild or retrigger tests with the older versions.

## Email report template

Be as elaborative as possible if applicable:
[ ] Explain in detail why its a regression
[ ] Show crashlogs (if applicable)
[ ] Show tools used to build the kernel
[ ] Show tuxmake/tuxrun reproducer
[ ] show build/runtime logfile (if applicable)

Example1:
```
<Explain what happens as detailed as possible>
Todays next kernel tag next-20240701 failed to boot arm64 devices built with
gcc-13.  No boot output was produced.

We have started to bisect this issue and get back with updates.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>


Tools versions:
ar/ld: ...
gcc: ...

To reproduce the build with tuxrun [2]:
tuxrun --runtime podman --device qemu-arm64 ...

To reproduce the build with tuxmake [3]:
tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13 ...

Links:
[1] https://path/to/tuxrun/repdoducer
[2] https://path/to/tuxmake/reproducer

--
Linaro LKFT
https://lkft.linaro.org
```

Example2:
```
Todays next kernel tag next-20240701 failed to boot an arm kernel on a qemu-armv7
devices, that was built with toolchain gcc-13.  The crashlog looks like this
(full logfile [1]):

<snippet of a crashlog>


We have started to bisect this issue and get back with updates.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>


Tools versions to build:
ar/ld: ...
gcc: ...

To reproduce the build with tuxrun [2]:
tuxrun --runtime podman --device qemu-armv7 ...

To reproduce the build with tuxmake [3]:
tuxmake --runtime podman --target-arch arm --toolchain gcc-13 ...

Links:
[1] https://path/to/the/full/test/logfile
[2] https://path/to/tuxrun/repdoducer
[3] https://path/to/tuxmake/reproducer

--
Linaro LKFT
https://lkft.linaro.org
```

```
Hi,

The mainline kernel v6.10-rc6 boot failed across all arm64 devices and
qemu-arm64 and no crash log found (earlycon) did not help.

But the defconfig builds boot PASS.

The boot problem is with defconfig + Extra Kconfigs and builds links
provided in the bottom of this email.

The boot test history shows that,
  GOOD: v6.10-rc5
  BAD:  v6.10-rc6

We are bisecting this issue and get back to you with git bisect results.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Following is the list of build combinations that boot failed.
Regressions found on qemu-arm64, Juno-r2, db410c, db845c, e850-96 and Rock-pi-4.
 - boot/gcc-13-lkftconfig-64k_page_size
 - boot/gcc-13-lkftconfig-kunit
 - boot/gcc-13-lkftconfig-rcutorture
 - boot/gcc-13-lkftconfig-16k_page_size
 - boot/gcc-13-lkftconfig-libgpiod
 - boot/gcc-13-lkftconfig-devicetree
 - boot/gcc-13-lkftconfig-debug-kmemleak
 - boot/gcc-13-lkftconfig-debug
 - boot/gcc-13-lkftconfig


Steps to reproduce boot failure on qemu-arm64:
----------
 - https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2idWuAb51mcz7lO1BAj8Aw0BrNY/reproducer

metadata:
----
  git_describe: v6.10-rc6
  git_repo: https://gitlab.com/Linaro/lkft/mirrors/torvalds/linux-mainline
  git_sha: 22a40d14b572deb80c0648557f4bd502d7e83826
  git_short_log: 22a40d14b572 ("Linux 6.10-rc6")
  arch: arm64

Links:
-----
 - https://storage.tuxsuite.com/public/linaro/lkft/builds/2idWrbdtwMqpD9wx7IPRGJ7Dsx3/
 - https://storage.tuxsuite.com/public/linaro/lkft/builds/2idWrYDposdlRsS4jwF916a0qGE/
 - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.10-rc6/testrun/24473346/suite/boot/test/gcc-13-lkftconfig-libgpiod/history/
 - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.10-rc6/testrun/24473903/suite/boot/test/gcc-13-lkftconfig-rcutorture/history/


--
Linaro LKFT
https://lkft.linaro.org
```