From the kernel-source git repository for SUSE kernels we can extract the people who backported a patch and the files a patch touches. Use this information to build a database for which paths are touched by which developers and write a tool to find the most relevant people for a given source path or upstream patch.

My friends have been using a supybot bot to help organizing weekly football matches. Over the years, there was demand for moving it to Telegram and supybot-telegram-bridge was born, allowing using the IRC bot in Telegram.

The result for xfstests in osd seems always red[1], but actually it's only a few test fail in a group(around 1/50). If we want to keep use openQA to handle those test, we need some enhancement for that. Try to enhancement test result to make it shows in a better way. - Make more reasonable group for those test

Diagnosing issues with stalling desktop application (or a whole desktop environment) is difficult these days as the application often requires multiple processes interconnected with sockets, pipes, futexes, etc. to work and often it is not clear which process is the one responsible for blocking the whole ecosystem. The idea of this project is to write a tool that gathers information about processes in the system and for each process that is sleeping display the resource (file, socket, futex) it is waiting on as well as the process that is likely responsible for unblocking (feeding pipe, sending data to socket, unlock futex, ...). Once the information is gathered, we can also plot it for graphical displaying with tools like graphviz.

Project Description

Just have play with bpftrace on some real kernel bugs.