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.129.124]) by sourceware.org (Postfix) with ESMTPS id E46D73858428 for ; Tue, 2 Jan 2024 22:13:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E46D73858428 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 E46D73858428 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1704233635; cv=none; b=YmnKBBK5Qbw8XYBv0ZE4d+YIhGPb9GbDKum60y4XjnUP//kzcE5E2ap6k1XXiy8ZxDSZvFNyVKd+YxWC6ibwN/pmZKUjgXWS6anl8cXWRn90huQTWgJK/6Wz71zlf3Ru61hxb3T/Pw7yxhkPHrfSg6lkR0O75LooLAUSR17jVZc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1704233635; c=relaxed/simple; bh=EqELmN3g/f6jl3NPxZ0iZcC4EI56cKTmzZUZiFzt4UY=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=SRj9sAtFo0TJuRF1p6S/1BsF0427izikQmE9RLDiCFujcXIEpAafT+LvuN5SrmwnLauKZanItx839e3K4whYYcL3Uj2KSyzF98kLMJbUZIHGaq0uJEXUiw91eZyqxfseKAAr3/UjE/Ie0Rg3yUPcXiN8R4u8Caqrs6yqG1GPhug= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1704233633; 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=Y6qd1MududlaK9yo3WglwIKsnhqKBNToO5xe8RKe0cg=; b=EtHsuxkXvP4O/G0qoVt3hXBTK2tAIekLMwdpftKN9z/c//+YWwKyRkYmRkHkrSbBKTszDQ yfTjxH3qEcvc9rYv/LSoG3uJRVZ8jqFDHs9woDJGhaw2Zb+rZW+FAg+eShpid07aGJXkBN Wj+p/l8G43HtuotThdd2KoPbg6fs3tA= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-661-TKOvSOrKOlaWe8t5XUQ2ag-1; Tue, 02 Jan 2024 17:13:52 -0500 X-MC-Unique: TKOvSOrKOlaWe8t5XUQ2ag-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 BF8AD3CBDFA7; Tue, 2 Jan 2024 22:13:51 +0000 (UTC) Received: from redhat.com (unknown [10.22.32.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B00ECC159B0; Tue, 2 Jan 2024 22:13:51 +0000 (UTC) Received: from [127.0.0.1] (helo=vm-rhel7) by redhat.com with esmtp (Exim 4.94.2) (envelope-from ) id 1rKn1C-0001JC-8q; Tue, 02 Jan 2024 17:13:50 -0500 From: fche@redhat.com (Frank Ch. Eigler) To: Maxim Kuvyrkov Cc: bunsen@sourceware.org, Christophe Lyon Subject: Re: bunsen to assist ci/cd testsuite historical analysis needs References: <20231212185006.GA21248@redhat.com> <86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org> Date: Tue, 02 Jan 2024 17:13:50 -0500 In-Reply-To: <86711582-4DD8-46F4-824C-583CB19EA58D@linaro.org> (Maxim Kuvyrkov's message of "Thu, 14 Dec 2023 18:45:02 +0300") Message-ID: <87wmsrjsdd.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 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 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_H4,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, Maxim - > How about a zoom/hangout/etc. call next week? [Christophe and I are > in Europe timezone.] I'm so sorry, I didn't see this in time. > One obvious opportunity is to make Linaro Toolchain CI submit results > to bunsen. Are there other things we can improve? To make this more concrete, your CI system could contribute to the sourceware bunsen pool of test results by: - creating a temporary git repo in your CI system - committing your local testsuite log files, and .bunsen.FOO build metadata files into your git repo using the bunsen t-upload-git-push shell script (or equivalent); see the sourceware buildbot master.cfg for the metadata specifics we use: https://sourceware.org/git/?p=builder.git;a=blob;f=builder/master.cfg;h=d2cb2d0ff1d68196ef1e8a8bcf9c9d7ceeb23211;hb=HEAD#l1267 - pushing each resulting branch/commit to the sourceware bunsen.git repo (we can get you ssh credentials sufficient for this) - deleting your local git repo if you like In this scenario, you wouldn't have to run any real bunsen code locally, nor publish any data or run a server of your own. The sourceware installation of bunsen would analyze and serve the data shortly after it hits git. If at some point, you became interested in more, like local long term analytics, or compressed log storage, or whatever, we can do something more sophisticated. - FChE