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 B39013857C64 for ; Thu, 11 Jan 2024 17:51:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B39013857C64 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 B39013857C64 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=1704995509; cv=none; b=N9SagjSMH1qVFdvLU7UnKb1CFyC8t9+BV6Y5eo1h+WJtNrZVUV48XYQwi0nI4bbu0Rbjhrpo1THoQt4fCfDpQjNHervNuR5Ur9lt+jDzGFaggRB5JDKVfRDzmK/1jUOUAQ/KxvKVk9KAWUFq+xsZ+POyHnNhOgea1BDlKwgzVyM= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1704995509; c=relaxed/simple; bh=r454dx+6UrnuHO/EyTBg1C7PzLwYW8NH/a7Nn6AHeN4=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=IDgPy4Wqrsbcf1CxA9wDWXZ197N0PWPUCjv7iQ4XX9XcVfGV/r4Wn2wTquAofffombuP/avnvtJFN7kQJVYEnZtOsVd9/G2Mt/gdZ3UkJxlvV6pLQJiUwiunbJWnGC5xBUn0qnZB1A3R8rUHL0DWR1jpGQFOSDCVHKqX0V3nGdw= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1704995507; 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=4gMnuFgYEqHbYM/dhAkd21LDCB+urH3tZfQxJrImJV8=; b=RPMSIrOTH/4CD/QX3lbj0V8X2p/2/hd0GlwEMtThSw93QYlNe3AHiXBPikoew3sdMobOPN Say9w3fcHR+LCXkP2jxp0anLw0hMeO75vPkNFBbDWXwTNXk1md/VIMemWa6xXyojfSdqef MIsntplhSz84U+BIYjx7sJYFRqhNmlA= 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-240-Gp0E1TkBPK2_rjCa4j7PTw-1; Thu, 11 Jan 2024 12:51:41 -0500 X-MC-Unique: Gp0E1TkBPK2_rjCa4j7PTw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (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 42890185A781; Thu, 11 Jan 2024 17:51:41 +0000 (UTC) Received: from redhat.com (unknown [10.22.8.114]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3312EC15A0C; Thu, 11 Jan 2024 17:51:41 +0000 (UTC) Received: from fche by redhat.com with local (Exim 4.94.2) (envelope-from ) id 1rNzDQ-0003SE-DX; Thu, 11 Jan 2024 12:51:40 -0500 Date: Thu, 11 Jan 2024 12:51:40 -0500 From: "Frank Ch. Eigler" To: Maxim Kuvyrkov Cc: bunsen@sourceware.org, Christophe Lyon Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs Message-ID: <20240111175140.GI28684@redhat.com> References: <20231212185006.GA21248@redhat.com> <86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org> <87wmsrjsdd.fsf@redhat.com> <20240104023400.GA17157@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.8 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=-8.3 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 - > > OK, will check that out. Is the git repo with results also visible somewhere? > [...] > [2] https://git.linaro.org/toolchain/ci/base-artifacts/tcwg_gcc_check/master-aarch64.git/ Just for reference, after a quick glance at this, it's close to but not quite verbatim usable by bunsen: - the .xz compression/extension would interfere with extension based matching - separating the .log and .sum files into different directories stops bunsen's crossmatching of the two; bunsen can accept the build tree raw locations of these files, without the "sumfiles" / "00-sumfiles" type of reorg - for buildbot builds on sourceware, we collect & parse the autoconf config.log files as first class content, rather than just informal console logs - bunsen would love to receive metadata about the build in little .bunsen.FOO text files, e.g. see: https://sourceware.org/git/?p=bunsendb.git;a=commit;h=613dd3b381b0910ebd5036fcf42761e2cead12ee I assume you had good reasons for .xz compressing these files inside the git repo ... but for what it's worth, we find that letting normal git-repack transparently manage all the compression of plain text payloads gives us excellent results. - FChE