Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 491092 - Automated collecting of build fails for QA
Summary: Automated collecting of build fails for QA
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo Linux bug wranglers
Depends on:
Reported: 2013-11-12 15:43 UTC by David Heidelberg (okias)
Modified: 2013-11-12 16:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description David Heidelberg (okias) 2013-11-12 15:43:21 UTC
My proposal is extend portage to gathering compilation logs for later analyze.

User (portage):

1. User select "I_WANT_IMPROVE_GENTOO=1" in make.conf.
2. USER="", PASS="" - There may be ability to send reports and view them online by entering user and pass.

3. # emerge -av package

a)portage check, if is used --nodeps, some totally crazy things and if so, then omit sending report
b) if overlay, check if has enabled sending report

a) When compilation successed, send emerge --info, with pkg and version.
b) When fails, same as a), but add build.log

1. gather information (+ remove duplicates, ignore junk)
2. make stats (most often failed packages)
3. deep analyze - package mostly fails with this flag, this compiler, this binutils etc.

1. xz compressed data ?
2. defined address where to send data for analysis

* simple BuildBot integrated in portage
* linking from bug to already created report (no need paste emerge --info and fail log)
* devs can see, what failing most often, what to focus to

Reproducible: Always
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2013-11-12 16:57:52 UTC
Please bring this to the gentoo-project mailing list.