Summary: | (Semi)Automatically report broken builds | ||
---|---|---|---|
Product: | Portage Development | Reporter: | skaumo <skaumo> |
Component: | Enhancement/Feature Requests | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | fturco, jstein, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
skaumo
2020-05-31 18:26:06 UTC
little addition: by systematically collecting statistics from packages that fail building above a certain threshold, it could be possible to automatically try to filter out such versions from world builds, or even attempt to build packages that depend on these easily-broken ones, or even go smart and find out with simple statistics of more fancy machine learning which configurations and/or USE flags cause the most breakages (think of chromium builds which decide to fail after 15 hours of hard work and 1 extra m³ of CO2 in the air) I agree, that this would be a nice tool to have. I remember a similar tool at debian https://wiki.debian.org/reportbug We have python libraries which provide most required functionalities for this script. Unfortunately this script will not be written by it self or by filing a ticket. If you read this and are interested in such a tool, start a new project with a GPL license. Ask on IRC #gentoo-dev-help, for hints. I am sure, you can motivate some developers to help you and to join. Please link the repository here, as soon there is one. |