| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01-12-2010 19:13, Alec Warner wrote: |
| 5 |
> On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto |
| 6 |
> <jmbsvicetto@g.o> wrote: |
| 7 |
> On 29-11-2010 10:34, Sebastian Pipping wrote: |
| 8 |
>>>> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote: |
| 9 |
>>>>> There will probably be no active version of Python set. |
| 10 |
>>>> |
| 11 |
>>>> You had two weeks to come up with this. |
| 12 |
>>>> |
| 13 |
>>>> Please find my on IRC to team up on an agreed fix. |
| 14 |
> |
| 15 |
> As Arfrever noted, this is likely the cause of the broken automated |
| 16 |
> weekly stages for this past week. By not having a python symlink / |
| 17 |
> wrapper, stages generation failed on stage2 run. |
| 18 |
> I'd like to take this chance to recall this is the 2nd time on the last |
| 19 |
> few months where stage generation was broken by python changes. Also, |
| 20 |
> we've been unable to create hardened stages for over 8 weeks because of |
| 21 |
> a sandbox issue. |
| 22 |
> The weekly stages generation depends on the quality and stability of the |
| 23 |
> "stable" tree. Therefore, the RelEng team kindly asks all maintainers to |
| 24 |
> pay attention to the stable ebuilds in the system set and to please fix |
| 25 |
> any failures asap as they may / can prevent stage generation. Be sure to |
| 26 |
> think carefully about changes that can impact the stage generation, in |
| 27 |
> particular when they involve python. |
| 28 |
> |
| 29 |
>> Two issues: |
| 30 |
> |
| 31 |
>> proj/en/releng is old as hell and doesn't even mention stage generation. |
| 32 |
|
| 33 |
Yeah, as everywhere else in Gentoo we could use more man power in RelEng. |
| 34 |
|
| 35 |
>> How does a developer know when the stage generation is broken? Is |
| 36 |
>> there a dashboard? At work we have a guy who is basically a build cop |
| 37 |
>> and checks our build dashboard once a day or so and if it is broken he |
| 38 |
>> goes and finds the guy who broke it and punches him in the face until |
| 39 |
>> he fixes it. I imagine we do not have staff for this (and no one has |
| 40 |
>> invented punching over the internet.) |
| 41 |
|
| 42 |
Lately I've become that guy for the amd64 and x86 builds. I've been |
| 43 |
going after maintainers to get the issues that are breaking stages |
| 44 |
fixed. I haven't tried "punching" anyone yet, though ;-) |
| 45 |
|
| 46 |
>> I am curious how often stage builds fail (how long can they be broken |
| 47 |
>> until we actually care?) |
| 48 |
|
| 49 |
They've been failing a bit in the past 6 months or so. We have some |
| 50 |
issues that affect all arches and others that affect specific arches. |
| 51 |
The worst and longest issue in the recent past was the mess with |
| 52 |
python-3.1 that lead to catalyst to die when python3 was becoming the |
| 53 |
main interpreter in stage1. We lost stages for a few months before we |
| 54 |
acted on that one. |
| 55 |
The previous issue that still affected this weeks stages build was the |
| 56 |
issue with sandbox that prevented any stages from being built for the |
| 57 |
past 2 months. |
| 58 |
This last issue with python was first reported for the ppc builds on |
| 59 |
20101128. I only found out yesterday when I was poked by Raúl (armin76) |
| 60 |
as I missed all Gentoo emails for the previous 10 days. |
| 61 |
For random issues I generally start worrying on the 2nd email. |
| 62 |
|
| 63 |
- -- |
| 64 |
Regards, |
| 65 |
|
| 66 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 67 |
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |
| 68 |
-----BEGIN PGP SIGNATURE----- |
| 69 |
Version: GnuPG v2.0.16 (GNU/Linux) |
| 70 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 71 |
|
| 72 |
iQIcBAEBAgAGBQJM9uYXAAoJEC8ZTXQF1qEPJkcP/jMau8sJ5UObjIGrGHeXODgB |
| 73 |
k76hNPm5j64jjqiQnqByevukIYQ0VfZhEbCcvRRdlMRzVfDoukmDx26372bZVO8d |
| 74 |
VkkS5JUmWxVR392W9flZqJw85DlrOB4p7HlxfjamgcsCxzrKVkKAqVDQcQkDGQOB |
| 75 |
qCOeDfLlijWOuc1bLMDUsQo1dYCr1XSKvsuY37lC6oQf5oCHr5a1+4xdhto1EbGr |
| 76 |
ASq3O9aKu/J+YLGI7rZtet5Lm8kAS803j6DLz0t15/I8obHzx+CeIzFLyr9Bly72 |
| 77 |
yL9DqU3aQ7xGFEI/GvCcS0vEOiile1VAT/YDLJAE3e24fs6r7Bf6PD1bUXoTiuAR |
| 78 |
tOGEJNwpj0Pa5lQoEs7Xe/xaY7W3YkoHe5QmyA8MNa2VyDpoMEm9HJkNH8IumyIn |
| 79 |
to68EOc4lHLHCYnm3CFa3C83jP6l3oq04VRlrs/D+geDP2rdTCCXvU8eg8O+c1NV |
| 80 |
buca8gK7iuA1sqHZWmInKSKp679Suw82rh7AxPJgXPc/YOzinhtBcMad3XmGmU4g |
| 81 |
XdoAXm5VWmO7/fj7ssCK9lzAWGn9ZaDKqGSl3rgpDkSTn7p7/Pih3OCcdcwoI/Gp |
| 82 |
uoJ/QD0eI8KAn6OTMN6UWr/i6P/Ys58m7dStKODsyboLejjtZMANbu1KiUKuumix |
| 83 |
AYLQ86te5Evz78MaFxeb |
| 84 |
=Yo6Y |
| 85 |
-----END PGP SIGNATURE----- |
Archives