| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This will help us find false positives (e.g. "disk full").
Change-Id: I5db9d333809f7067dc5dff81544e9e5f0206ee8c
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
|
|
|
|
|
|
| |
"Successful" incremental builds can also be an error, if a clean build
fails for the same project.
Change-Id: I9f52d840fbda53a906c039e1ee0db2c656db6f8e
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
|
|
|
|
|
| |
This should increase the likelihood of errors.
Change-Id: I9a7b0fded12db05bc55e2f557d220a2614b73d62
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
Incremental builds are the likeliest source of problems, as well as the
one that is the hardest to reproduce. This new tool turns a given project
into a quasi-autotest by checking out random commits and doing incremental
builds on them. In case of a build error that is not reproducible with
a clean build, it aborts and reports the offending sequence of commits.
Any qbs project that comes in a git repository is supported.
Change-Id: I9f6f9172ce03140341ed25859092a8ed32d4a17d
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|