From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 0F32F1F8C8 for ; Fri, 8 Oct 2021 21:57:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243501AbhJHV7T (ORCPT ); Fri, 8 Oct 2021 17:59:19 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:55245 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231774AbhJHV7S (ORCPT ); Fri, 8 Oct 2021 17:59:18 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 73A1BE3E61; Fri, 8 Oct 2021 17:57:22 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=m/Jn8GEMKVqVg9edieRjmWz0hHt6RDhiPK9Sjv XSSoQ=; b=f43LrSwEJJbuluuGi+acp/rSF11aHraKkK/iF+YeOZHe0A+oagYch0 sP1K+FiEBXeuoF4Uv+mwyRVb/zvNNm8HCAltdkNO4cwhApZD3p4G8SsEMEfnq5Ln 0ioMC7FzO5iBqfnckFzc5Ay4uPuxJZlWWa5zTgpp8TH8T4SXYkASk= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 6C783E3E60; Fri, 8 Oct 2021 17:57:22 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [104.133.2.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 580BCE3E5F; Fri, 8 Oct 2021 17:57:21 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Jeff King Cc: =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Taylor Blau , git@vger.kernel.org Subject: Re: What's cooking in git.git (Oct 2021, #02; Wed, 6) References: <87sfxdgtpu.fsf@evledraar.gmail.com> Date: Fri, 08 Oct 2021 14:57:20 -0700 In-Reply-To: (Jeff King's message of "Fri, 8 Oct 2021 16:19:46 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: B6778072-2882-11EC-A962-CD991BBA3BAF-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Jeff King writes: > On Fri, Oct 08, 2021 at 01:03:08PM -0700, Junio C Hamano wrote: > >> I usually have at least two pushout of 'seen' (one with the full set >> of 'seen' including known-to-be-broken topic integrations, the other >> with seen~$some_hopefully_small_number that I didn't see brekaage in >> my local build), and then on graduation days 'next' and 'master' are >> also updated, so 3 is cutting very close ;-) > > Hmm, yeah. They say "21 builds per week", which would be plenty (you > don't push out integrations every day), 'seen' is pushed out every day (not on weekends), though. > I'm not sure what happens when you hit the limit. If it just silently > skips the analysis, that's fine (we'll pick up the changes the next > day). If it causes a CI failure that nags you, that is less good. But > probably something we could work around in the Actions commands. Yup.