openSUSE code

Description

I had presented the "Wicked Network Manager" talk at openSUSE Asia summit @Beijing. I would like to keep studying the topic continuously. Getting involve the source code and study the operating style and components. I also met some problem after discussing and testing issues while my research , I want to keep it as a record and writing the technical document on wiki too.

The Idea

Since some time I am interested in getting better at C++ and learn more about Qt framework. Since I learn best with having a project/goal I came up with this:

There is a running gag built into openQA called interactive mode. It goes like this: "if you need the interactive mode, it's broken". The reason: the so called interactive mode is a collection of hacks - in theory making it possible to update needles in a running test.

This is an idea that's been kicking around for a while... maybe it's finally time to "make it so."

Learning design model can help to produce high quality codes, which will benefit our products.

Bisection is a well known method of localizing which commit caused a regression in a code repository. git-bisect is a particularly used tool for this problem in git repositories. However it is often the case that the failure is probabilistic in nature - either because we don't have a reliable reproducer of the failure and thus not reproducing a problem on a particular commit does not mean the problem is not still present there, or because of inherent variability of e.g. performance regressions. Bisection for such failures is problematic as it takes only one false result for the bisection to end up in an unrelated part of code history. So in these cases we usually have to heavily extend runtime of a reproducer or do multiple test runs or multiple bisection runs to minimize a chance of error.

Project Description