public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: A new bugzilla keyword for bug investigation
Date: Sun, 19 Jan 2025 17:19:07 -0000 (UTC)	[thread overview]
Message-ID: <pan$7f1a3$ddc7d37f$2d7c0b84$de5b9176@cox.net> (raw)
In-Reply-To: 87o704m23x.fsf@gentoo.org

Sam James posted on Sat, 18 Jan 2025 18:02:58 +0000 as excerpted:

> Agostino Sarubbo <ago@gentoo.org> writes:
> 
>> 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.
> 
> Prompted by a comment on the bug...
> 
> "needs-investigation" might sound like IN_PROGRESS or someone is working
> on the bug, rather than signalling they need help from someone else.

Maybe simply and most literally/clearly:

no-clear-error

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2025-01-19 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  8:17 [gentoo-dev] A new bugzilla keyword for bug investigation Agostino Sarubbo
2025-01-10 16:03 ` 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   ` Duncan [this message]
2025-01-18 19:55 ` 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='pan$7f1a3$ddc7d37f$2d7c0b84$de5b9176@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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