From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: soap@gentoo.org
Subject: Re: [gentoo-dev] A feedback about the CI bug reporting system
Date: Sat, 07 Nov 2020 12:30:00 +0100 [thread overview]
Message-ID: <2675892.Y6S9NjorxK@spectre> (raw)
In-Reply-To: <2044703.irdbgypaU6@spectre>
On venerdì 6 novembre 2020 08:21:39 CET Agostino Sarubbo wrote:
> Hello all,
>
> 6 months have been passed after the CI system started to file bug reports.
> ~ 4700 bugs have been submitted
>
> We _know_ that atm is not possible to set a specific summary, instead a
> generic summary is used in case of compile failures and test failures.
> There are also some documented limitations.
>
> If there aren't much commits, usually you get the bug after 30 minutes after
> the commit and this looks to be nice.
>
> Since there are conflicting opinions I would like to know if you find it
> useful or not.
>
> More info about the project here:
> https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/
>
> Please keep me CC'ed
>
> Thank you
> Agostino
Thanks all for the feedback.
What looks strange is that ci/tinderbox opened ~4700 bugs, sure, there are
invalid/duplicate bugs but the majority are fixed so in my opinion they were
useful, but looking at the mailing list feedback looks to be a completely
crap.
I want to play the game of destructive people but in a constructive way.
Thanks to @gyakovlev for the idea I have opened a new github project where we
can collect the requests and the bugs:
https://github.com/asarubbo/ci/issues
An important note:
I consider this 'project' as something related to QA ( if you have a different
opinion feel free to say ), so since I received rant from developers for
something requested by other developers, I will touch the code ONLY when there
is the QA lead approval.
When you want a new feature or you want to modify something that already
exists, please open a thread (gentoo-dev is fine, and thanks to bman for the
tracking idea) and open a github issue only when there is a written track of
the QA lead approval mentioned above.
There is a README into the repository that explains all class of bugs
discovered by the CI system.
Thank you
Agostino
next prev parent reply other threads:[~2020-11-07 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 7:21 [gentoo-dev] A feedback about the CI bug reporting system Agostino Sarubbo
2020-11-06 8:18 ` Joonas Niilola
2020-11-06 8:39 ` Agostino Sarubbo
2020-11-06 15:31 ` Aaron Bauman
2020-11-06 11:03 ` Agostino Sarubbo
2020-11-07 9:49 ` Agostino Sarubbo
2020-11-06 9:14 ` Michał Górny
2020-11-06 15:37 ` Aaron Bauman
2020-11-07 6:15 ` Robin H. Johnson
2020-11-07 8:26 ` Agostino Sarubbo
2020-11-07 10:52 ` Andreas K. Hüttel
2020-11-07 11:30 ` Agostino Sarubbo [this message]
2020-11-07 16:06 ` Thomas Deutschmann
2020-11-07 16:53 ` Agostino Sarubbo
2020-11-09 12:13 ` Marek Szuba
2020-11-09 12:29 ` Agostino Sarubbo
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=2675892.Y6S9NjorxK@spectre \
--to=ago@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=soap@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