Gentoo Archives: gentoo-dev

From: "M. J. Everitt" <m.j.everitt@×××.org>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Common rsync-gen errors, why they happen, and what you can do about it
Date: Wed, 18 Jan 2017 09:16:20
Message-Id: 416de5fb-36a0-0080-40f5-219d6baea61a@iee.org
In Reply to: Re: [gentoo-dev] Re: Common rsync-gen errors, why they happen, and what you can do about it by Kent Fredric
1 On 18/01/17 09:04, Kent Fredric wrote:
2 > On Wed, 18 Jan 2017 08:19:19 +0100
3 > Dirkjan Ochtman <djc@g.o> wrote:
4 >
5 >> <snip>
6 >> That makes sense. My other comment initially reading your email would
7 >> be, send those emails to gentoo-core or -project or whatever. If
8 >> others don't get to feel the pain (of every half-hour error emails,
9 >> for example), they will be much less compelled to fix the problem. So
10 >> absorbing this "pain" into just you or infra makes us less scalable as
11 >> a distribution, and less likely that someone will feel motivated to
12 >> add the extra bits of automation (like a git hook) that will make this
13 >> problem go away.
14 > +1 , I was aware that "somebody" knew the tree was breaking, but I had
15 > no understanding of what was breaking, why it was breaking, or even how
16 > people knew it was breaking.
17 >
18 > And so upon reading the original email hearing that people could
19 > even be notified of this fact, made me immediately question what I should
20 > be doing to see said notifications, or if there was even a page
21 > that I could check periodically to know what the state of the sync was.
22 >
23 > As the saying goes, information and awareness of the problem is a critical
24 > first step to solving the problem.
25 Is this something that could be woven into the
26 "gentoo-automated-testing" mailing-list ? Ever since I've been poking at
27 mgorny+ 's efforts into CI I've been subscribed, and it would be a
28 useful central place to put such reports. Is that viable?

Attachments

File name MIME type
signature.asc application/pgp-signature