From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id DC4F93858D20 for ; Tue, 16 Jan 2024 17:10:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DC4F93858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DC4F93858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705425034; cv=none; b=PJuY7QEOspwi23WDqU5I4dIsNUIgWYQ+rz4EeF59ncBrc1VemInnWE9UsONt8IP7lwGGk7ZdbJfz8jjTBb6vS1H/TLzgpjpqqlQPwz+ji2GYL9+LMGsH0eiNsnoRgym+Xmwl53hALqq8ewW7GA0JsTJHu1Z9ksjPXaTA/elpOgw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1705425034; c=relaxed/simple; bh=fpG3PHAYf57QjYbk5r3vvh/q0NSjT0/BYxyohKxO14w=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=ADtkh3V53w0uTgvNeU995eRkJTYPbRqHJwgwCs7wkmQCj4no/CfyhMQo35vyphNXpo2phPUgR39rm3u1RDLBQ7zae2CsXzD2UpEVsCUL8ZPuEFLX0jlQHZv/YOWTjbg5+UjovDk19JAZFrC2aL0+qdy9uIhsSpzjcs7pGDK+ujk= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1705425028; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=x+wb0ihlud/8hRrloJEQqH1QSuSR6A4GlzhDWkOiO5Q=; b=itgnVEK5GFYkW/QlFs7LMXmgNyXnjp52LaFopxUKpYQyh7ZpfbvbF+UiTWjguMh7ufEWzF XR4UKe5Bk4ZVQGfQcuftq7k6+3d+YFoNmwCigQadSlO0fFvGfeftMuoluA64C0PpSnRMh+ 9I5VGrvXglAlcZl6PEFcy39amhJ9bkY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-294-WDmYQ44HNR-DdDn9fAUOHg-1; Tue, 16 Jan 2024 12:10:22 -0500 X-MC-Unique: WDmYQ44HNR-DdDn9fAUOHg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7E169185A787; Tue, 16 Jan 2024 17:10:18 +0000 (UTC) Received: from redhat.com (unknown [10.22.8.6]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6F2431121312; Tue, 16 Jan 2024 17:10:18 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1rPmx7-0002aS-Gn; Tue, 16 Jan 2024 12:10:17 -0500 Date: Tue, 16 Jan 2024 12:10:17 -0500 From: "Frank Ch. Eigler" To: Christophe Lyon Cc: Maxim Kuvyrkov , bunsen@sourceware.org Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs Message-ID: <20240116171017.GH26700@redhat.com> References: <20231212185006.GA21248@redhat.com> <86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org> <87wmsrjsdd.fsf@redhat.com> <20240104023400.GA17157@redhat.com> <20240111175140.GI28684@redhat.com> <7AE27BD9-5332-496D-9A32-C49383A039B3@linaro.org> <20240116161520.GF26700@redhat.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-7.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi - > > Interesting. In the bunsen model, that would be better represented as > > individual testrun commits for each of the run attempts, including the > > Do you mean each testrun includes the whole testsuite? Each testrun includes just as much of the testsuite as you wish. > In our case, only the first run includes the whole testsuite, the > subsequent ones include only the .exp files for which we detected > failures, to keep testing time reasonably low. That makes sense (unless you get a false positive PASS in the first run, don't bother rerun, and miss the flake!). In any case, bunsen would gladly accept the logs generated from each of the partial reruns. - FChE