|
Description
Dane Smith (RETIRED)
2011-01-13 13:58:06 UTC
what exactly is the point of this tracker ? how is having this information useful in any way ? (In reply to comment #1) > what exactly is the point of this tracker ? how is having this information > useful in any way ? > The tinderbox will be reporting them soon hopefully and I felt this was the simple way to keep track of them. This is fixed in farstream 0.2.1 btw Does this tracker cover build failures caused by using parallel make? The wording of the summary seems to indicate it is only for packages which ignore MAKEOPTS completely, which use -j1, or which produce the “make jobserver unavailable” message. (In reply to comment #4) > Does this tracker cover build failures caused by using parallel make? The > wording of the summary seems to indicate it is only for packages which > ignore MAKEOPTS completely, which use -j1, or which produce the “make > jobserver unavailable” message. This should be used for any parallel make related issues. If the build fails with -jX where X > 1, they should be tracked here. Also, ebuilds which are forcing -j1 aren't "fixing" the issue. They're merely hacking around it. We should probably be tracking those here as well. This tracker is not useful anymore. Discussed today on #gentoo-qa qgrep "j1" | wc -l returns 1243 hits (with a few false posisitves) Parallel build bugs linked here belong to one of the two types a) it is not fixed with -j1 and the package is broken and should be fixed in short time. b) we have a forced -j1 in the ebuild and can track it better with a qa script Reopened on request. Please collect knowledge on troubleshooting in the wiki https://wiki.gentoo.org/wiki/Troubleshooting_parallel_builds |