*

Kernelci.org automated bisection

Guillaume Tucker avatar

Posted on 16/01/2018 by Guillaume Tucker

Share this post:

The next step in Linux kernel testing: automatically finding commits that cause failures to boot.

About kernelci.org

The kernelci.org project aims at continuously testing the mainline Linux kernel, from stable branches to linux-next on a variety of platforms. When a revision fails to build or boot, kernel developers get informed via email reports. A summary of all the results can also be found directly on the website.

Automated bisection

When a kernel revision fails to boot, while it is reported in the emails it is not always obvious what caused the problem. Development branches get typically merged with many commits on them, and only one boot test is run after the merge. So the initial information is that the main branch used to work, and after these many commits got merged it started failing. The actual problem can be very hard to track down.

For a given set of bad and good revisions, it is possible to run more boot tests while using Git’s bisection feature to determine which one to test next until there is only one left. Ideally, this should be the one that caused the breakage. However there are many subtleties that complicate things, for example there may be several changes introducing different problems especially if the initial range of revisions is very wide. Also, failures to build some revisions or false positives from the boot tests can mislead the bisection logic and land on a change that is not the actual breaking one.

So, does it work?

There is currently an experimental feature to automatically run a bisection for each boot regression found on kernelci.org. This will be started with the known good/bad revisions, on a given platform, in a given lab, with a given config. It is already starting to show some useful results, for example:

The main challenge is to bring the results to a high level of quality before actively publishing them. False positives in this area can be very harmful: if the bisection finds a change that is not responsible for the breakage, reporting it can be counterproductive. Developers may spend time chasing a red herring and lose trust in the reports. For this reason, each valid bisection result is currently manually verified, curated and shared on mailing lists or by contacting individuals directly.

Next steps

We’re now in a maturing phase, identifying issues with the bisection tool and improving it until it’s ready for production. This will initially target only boot tests on mainline and stable branches. Future improvements can include extending it to more kernel trees, bisecting linux-next against mainline and covering more functional tests beyond booting to a prompt.
 


Visit Guillaume's blog.

Comments (0)


Add a Comment






Allowed tags: <b><i><br>Add a new comment:


Latest Blog Posts

Quick hack: git-pw

18/04/2019

A well-known Linux kernel developer once said, a poor craftsman famously complains about his tools, but a good craftsman knows how to choose…

An eBPF overview, part 2: Machine & bytecode

15/04/2019

The second part of this series takes a more in-depth look at the eBPF VM and program studied in the first part. Having this low level knowledge…

An eBPF overview, part 1: Introduction

05/04/2019

Interested in learning more about low-level specifics of the eBPF stack? Read on as we take a deep dive, from its VM mechanisms and tools,…

Running Android next to Wayland

01/04/2019

It's now possible to run Android applications in the same graphical environment as regular Wayland Linux applications with full 3D acceleration.…

Modern USB gadget on Linux & how to integrate it with systemd (Part 2)

27/03/2019

In the previous post I introduced you to the subject of USB gadgets implemented as machines running Linux. In this post, we look at how…

Bootstraping a minimal Arch Linux image

20/03/2019

In this tutorial, we'll look at how to create a functional and simple Arch Linux virtual machine image, that can have network access, display…

Open Since 2005 logo

We use cookies on this website to ensure that you get the best experience. By continuing to use this website you are consenting to the use of these cookies. To find out more please follow this link.

Collabora Ltd © 2005-2019. All rights reserved. Website sitemap.