Gentoo Archives: gentoo-dev

From: Ian Stakenvicius <axs@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] A constructive reommendation on stablity improvemt
Date: Tue, 12 Aug 2014 14:13:15
Message-Id: 53EA20ED.6070009@gentoo.org
In Reply to: Re: [gentoo-dev] A constructive reommendation on stablity improvemt by Thomas Kahle
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 On 10/08/14 05:03 PM, Thomas Kahle wrote:
5 > Hi,
6 >
7 > On 09/08/14 18:18, Igor wrote:
8 >> Hi all,
9 >>
10 >> Hereby the summary of my personal suggestions to increase GENTOO
11 >> stability and help it's maintainers and developers.
12 >>
13 >> 1. make.conf
14 >>
15 >> Add
16 >>
17 >> BUG_REPORT_URL "http://"(or similar name) BUG_REPORT ON/OFF
18 >> BUG_REPORT_LEVEL
19 >>
20 >> to make.conf
21 >
22 > Apart from the huge work to implement this, I think any automatic
23 > reporting of build failures will not be useful due to a very bad
24 > signal to noise ratio. Bug wrangling will be insane. What are the
25 > experiences in the industry. Is Mozilla getting anything useful
26 > out of their automatic crash reports?
27 >
28 > Cheers, Thomas
29 >
30 >
31
32
33 I haven't been able to track down the right people in mozilla to ask,
34 yet. I have seen some bugs where the developers that work on fixing
35 an issue are indeed referencing the crash dumps that were submitted; i
36 don't know if or how well the crash report submitting links multiple
37 crashes together to the same issue, though.
38
39 Mozilla also has a very hefty 'try' (tinderbox) system, though, that
40 runs builds on every single commit across every platform that is
41 supported -- I believe they have a number of tools that help aggregate
42 the errors and warnings from those logs to provide useful output to
43 support development, and I think that model might be more comparable
44 to what we would need in Gentoo -- essentially, this project Igor is
45 suggesting would turn the Gentoo community into one massive tinderbox.
46
47
48 -----BEGIN PGP SIGNATURE-----
49 Version: GnuPG v2
50
51 iF4EAREIAAYFAlPqIO0ACgkQ2ugaI38ACPBfaAD+IKBIQWf0L4WF2pd6iCzdDUU0
52 l11GSV6NfnpQYG/qilYBAI+bEUHYqxA75Uhrg+m9lqJ0CzwBpm4Tn0ya1MzmiXxC
53 =gi7Q
54 -----END PGP SIGNATURE-----