public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A constructive reommendation on stablity improvemt
Date: Sun, 10 Aug 2014 07:59:09 +1200	[thread overview]
Message-ID: <CAATnKFAhD83d+CWt=LEbNvvCeUyCXjTwTebA2OJ04waWhgEQ=A@mail.gmail.com> (raw)
In-Reply-To: <20140809212239.181e15f6@marga.jer-c2.orkz.net>

[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]

On 10 August 2014 07:22, Jeroen Roovers <jer@gentoo.org> wrote:

>
> Example 2: Mr. I.B. User configured his system with CFLAGS=-fomg-faster
> and now it generates a ton of build failures. All of these should go
> to /dev/null, but there we are running an automated service that cannot
> be taught how to distinguish between genuine bug reports and PEBKAC.
>
> The problem: How do you propose to filter out all the junk and promote
> genuine issues to "bug reports"?
>
> Both examples should make clear why we have a bug tracker and not an
> automated build failure reporting facility - it works rather well and
> it stops dead a lot of spam and bad reports.


^ In practice this doesn't prove to be an issue for CPAN, *because* it uses
a seperate channel from the bug reports.

The isolation means you can either choose to delve into the metrics, or
simply ignore them, they don't affect your workflow unless you want them to.

Users with misconfigured systems do occur from time to time, and you just
get a knack for knowing which reports are reports you can fix, and which
you just leave to rot.

And there's no *onus* on you to fix anything, because its only an automated
report, its intended to give you installation context *if* and *when* you
want it, as opposed to interrupting you and demanding attention.

For instance: http://matrix.cpantesters.org/?dist=IO+1.25

This shows the CPAN version of IO can't be installed on >5.18, on windows
and a few darwin boxes.

The maintainer of IO doesn't *HAVE* to do anything here, its just
information they can go swimming for if they want to.

=~ Its up to the maintainer if they want to respond to this information or
not.

If a user desires a response, they still have to file a bug report.


Though it does prove useful as a user filing a bug report to be able to see
all the other failure reports and know "Hey, its not just me, this is a
real problem and I'm not making it up", and be able to link to a bunch of
them, which cross comparison quickly reveals common elements to investigate
as probable failing points.

But I'm very much in agreement that such as system should NEVER be attached
as a pump handle to bugzilla itself.


-- 
Kent

*KENTNL* - https://metacpan.org/author/KENTNL

[-- Attachment #2: Type: text/html, Size: 3408 bytes --]

  reply	other threads:[~2014-08-09 19:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 16:18 [gentoo-dev] A constructive reommendation on stablity improvemt Igor
2014-08-09 17:42 ` Kent Fredric
2014-08-09 18:15   ` Igor
2014-08-09 19:22     ` Jeroen Roovers
2014-08-09 19:59       ` Kent Fredric [this message]
2014-08-10  0:41         ` Tim Boudreau
2014-08-10 18:53           ` Igor
2014-08-10 21:05       ` Thomas Kahle
2014-08-09 19:49     ` Kent Fredric
2014-08-10 19:02       ` Igor
2014-08-10 21:03 ` Thomas Kahle
2014-08-12 14:13   ` Ian Stakenvicius

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAATnKFAhD83d+CWt=LEbNvvCeUyCXjTwTebA2OJ04waWhgEQ=A@mail.gmail.com' \
    --to=kentfredric@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox