From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] A new bugzilla keyword for bug investigation
Date: Fri, 10 Jan 2025 09:17:59 +0100 [thread overview]
Message-ID: <2645278.Lt9SDvczpP@fcf> (raw)
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Good morning everyone,
during tinderbox activity I realized that sometimes there are bugs with unknown causes at
the time of filing.
Examples are:
- no "error: " string
- mysterious test failures
- hidden bugs on build.log but present on config.log and/or additional files
- bugs that may be related to new toolchain components, but not clearly stated
For that reason I would like to propose a new bugzilla KEYWORD, like:
- NEEDS-TRIAGE
or
- NEEDS-INVESTIGATION
or whatever you think is better.
With that KEYWORD we can set-up a saved search and 'experienced' devs can help to
diagnose the issue.
This KEYWORD is supposed to be set manually and not supposed to be set automatically
when there is a missing "error: " string. And obviously it can be used by everyone that
needs help.
Before send this to the mailing list, I talked about that with sam (since he is one of those
who does this activity) and agreed.
What do you think?
Agostino
[-- Attachment #2: Type: text/html, Size: 2388 bytes --]
next reply other threads:[~2025-01-10 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:17 Agostino Sarubbo [this message]
2025-01-10 16:03 ` [gentoo-dev] A new bugzilla keyword for bug investigation Jaco Kroon
2025-01-10 16:12 ` Rich Freeman
2025-01-10 16:34 ` Immolo
2025-01-11 6:53 ` Agostino Sarubbo
2025-01-18 18:02 ` Sam James
2025-01-19 17:19 ` [gentoo-dev] " Duncan
2025-01-18 19:55 ` [gentoo-dev] " Jonas Stein
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=2645278.Lt9SDvczpP@fcf \
--to=ago@gentoo.org \
--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