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 (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9AAA7158041 for ; Fri, 23 Feb 2024 14:35:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BA2CDE2A90; Fri, 23 Feb 2024 14:35:37 +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) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 76A8FE2A8C for ; Fri, 23 Feb 2024 14:35:37 +0000 (UTC) From: Agostino Sarubbo To: "gentoo-dev@lists.gentoo.org" Subject: [gentoo-dev] Important note on tinderbox behavior Date: Fri, 23 Feb 2024 15:35:33 +0100 Message-ID: <6674250.4vTCxPXJkl@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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: cc009944-f458-4f1a-8a90-64241e3fe341 X-Archives-Hash: 1f166d08fda5d2274e956298b0be5995 Dear all, TL;DR: tinderbox will skip packages with know failures it's a matter of fact that on bugzilla there are hundreds of bugs that tinderbox continues to reproduce. That results in a waste of resources and time. What was done to improve this situation: in the past few months I launched few tinderbox environments with the scope of collect the known failures. These failures, that have an open bug, have been noted on a list. When tinderbox starts, it queries bugzilla to understand the status of the bug and in case of open bugs it passes the package names to emerge as --exclude $PACKAGE That save a lot of time because emerge FOO --exclude FOO hangs immediately. Imagine a scenario where a broken package has no DEPEND. The waste of resource is very minimal. Imagine another scenario where: - the package FOO is broken - the package BAR has 100 depend - the package FOO is a depend of BAR - the package FOO is at position 100 of the depend order that results in build 99 packages for nothing. In short the problem is not in the package itself, but when a lot of DEPEND are involved. This behavior, *that was already experimented in the latest few months* does not change anything on your side. The only con that comes in my mind is that when a version bump silently fixes an issue and maintainer is not aware about that. The bug still remains as open and as a consequence, the package continues to be excluded. For this reason, please be pay more attention to open bugs. As a side note, bugs are obviously categorized. For example a build failure for a package FOO on musl, will produce '--exclude FOO' only on musl. Same thing for doc brokeness. For this reason please expect less 'tinderbox has reproduced this issue with version "${VERSION}" - Updating summary.' and not seeing anymore this message is not a symptom of 'this is fixed now' ( https://bugs.gentoo.org/770889#c6 ) Failures regarding Modern C porting are excluded from this behavior. Instead '-fpermissive' will be used to build as much as possible. Tests failures have also no influence on that, but keep in mind that packages with known test failure(s) are not built by default. Thanks Agostino