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 1E8573858C53 for ; Mon, 19 Sep 2022 19:56:07 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1E8573858C53 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1663617366; 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; bh=QsTes+fj6JpDs7tsgxUnN5TEjz1N10WnR3Kr8/KplVg=; b=N7yrRKIVgZYbYvdA+3xpbEtrNDNFFIBI6zYdOzSergl0uagzwXKj/DspOYlbk2T8HbM84Q nngXIX0pxn5EHHkXbR5wUPi3p7HzzDCwDuE+qTH7C3oQbCEcG8PC6obIT317/3YoWWB10V u0Onv2Eg8uW1XhyjTipVcvolU9+rOlY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-675-YZof-MRlMyGv-bvJtJKONw-1; Mon, 19 Sep 2022 15:56:03 -0400 X-MC-Unique: YZof-MRlMyGv-bvJtJKONw-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D26C68828C3; Mon, 19 Sep 2022 19:56:02 +0000 (UTC) Received: from greed.delorie.com (unknown [10.22.8.19]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B77CB140EBF5; Mon, 19 Sep 2022 19:56:02 +0000 (UTC) Received: from greed.delorie.com.redhat.com (localhost [127.0.0.1]) by greed.delorie.com (8.15.2/8.15.2) with ESMTP id 28JJtpa72487519; Mon, 19 Sep 2022 15:55:52 -0400 From: DJ Delorie To: "Carlos O'Donell" Cc: siddhesh@gotplt.org, libc-alpha@sourceware.org Subject: Re: Run TryBot-apply_patch on the full queue? In-Reply-To: Date: Mon, 19 Sep 2022 15:55:51 -0400 Message-ID: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,SPF_NONE,TXREP 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: "Carlos O'Donell" writes: > The curator/runners are a more advanced "patchwork bot" framework that > can do very specific things. I think it might be wise to keep the trybot API the same, though. I mean, if we have a "patch applies" trybot, it can be controlled by the current curator (once per patch seen) as well as by a patchwork bot that retries all patches once a day. Both systems just need to inject the right json into the trybot's queue, and that information comes mainly from patchwork anyway. The "do once per patch" case is still common (and important) enough to warrant a centralized curator though.