From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 5BB6215813A for ; Fri, 10 Jan 2025 08:18:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5CA7DE07DB; Fri, 10 Jan 2025 08:18:04 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E306CE07D4 for ; Fri, 10 Jan 2025 08:18:03 +0000 (UTC) From: Agostino Sarubbo 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 Message-ID: <2645278.Lt9SDvczpP@fcf> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart4406425.ejJDZkT8p0" Content-Transfer-Encoding: 7Bit X-Archives-Salt: a8798dc6-8833-493a-9e9f-ae9688748528 X-Archives-Hash: ea9994ba4ff2a81025fb5e1918b6b6bf This is a multi-part message in MIME format. --nextPart4406425.ejJDZkT8p0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 --nextPart4406425.ejJDZkT8p0 Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="utf-8"

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

--nextPart4406425.ejJDZkT8p0--