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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D7AAC1382C5 for ; Mon, 3 May 2021 10:07:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D953CE0822; Mon, 3 May 2021 10:07:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9F6CAE078A for ; Mon, 3 May 2021 10:07:11 +0000 (UTC) From: Agostino Sarubbo To: gentoo-dev@lists.gentoo.org Cc: sam@gentoo.org, zlogene Subject: [gentoo-dev] CI and be CC'ed in a bug report Date: Mon, 03 May 2021 12:07:01 +0200 Message-ID: <1858564.PYKUYFuaPT@spectre> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: ecd741c7-a223-489d-b7ab-1a579f66307c X-Archives-Hash: 8ee5c9e3ef549c62e33abcb1ecdbedfd Hello, I've noticed that it's been in vogue lately say "as you were asked many times" when there is something to say. Well, this often (always?) happens without a reference but I don't care. As asked by sam, CI should CC people that are breaking stuff with their commits, see: https://cutt.ly/Wbx08SQ However since there are message like this: https://cutt.ly/vbx2qv2 I'm giving a public explanation about what is happening: 1) Compilation of package 'A' works as expected 2) A new major change is introduced (gcc/glibc/binutils) 3) The CI system always runs an updated system, then it uses latest ~arch versions 4) Someone touches the package by introducing a simple comment in the ebuild 5) Since the ebuild was touched, the CI tries to compile it 6) Package 'A' fails to compile because of GCC-11 and not because of the comment added into the ebuild. This happens mostly when the entire tree has not been 'tinderboxed' with the new major change. So Mikle, I have nothing to fix. For the record, if you want to request a change, you should send at least an email or open a ticket. Send a message somewhere (mostly IRC) and say "as you were asked many times" just seems to be unproductive (or unprofessional, it depends on the point of view) As a side note, as written before and reminder: who does not want to receive email/reports from tinderbox and ci may request to be in the exclusion list. Agostino