Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 28 |
Nodes: | 6 (1 / 5) |
Uptime: | 46:11:04 |
Calls: | 422 |
Calls today: | 1 |
Files: | 1,024 |
Messages: | 90,336 |
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.
[...]
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 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.
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
On Fri, Jan 10, 2025 at 3:17 AM Agostino Sarubbo <ago@gentoo.org> wrote:
For that reason I would like to propose a new bugzilla KEYWORD, like:
- NEEDS-TRIAGE
or
- NEEDS-INVESTIGATION
Makes a lot of sense, though I'm not sure if it could cause confusion
for bug wrangling/etc. I don't think non-prived bugzilla users could
add the keyword though, so probably no impact there?
The bug wranglers might actually like it for marking stuff that can't
be assigned easily? In any case, I'm just thinking out loud about
whether there is anything in the bug wrangling process that needs consideration.
--
Rich
For that reason I would like to propose a new bugzilla KEYWORD, like:
- NEEDS-TRIAGE
or
- NEEDS-INVESTIGATION
Makes a lot of sense, though I'm not sure if it could cause confusion
for bug wrangling/etc. I don't think non-prived bugzilla users could
add the keyword though, so probably no impact there?
The bug wranglers might actually like it for marking stuff that can't
be assigned easily? In any case, I'm just thinking out loud about
whether there is anything in the bug wrangling process that needs consideration.