Re: [quicwg/base-drafts] Cache git repo, draft references in Circle (#3009)

Martin Thomson <notifications@github.com> Mon, 09 September 2019 01:08 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DE9120059 for <quic-issues@ietfa.amsl.com>; Sun, 8 Sep 2019 18:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hD7K7EF8tWtT for <quic-issues@ietfa.amsl.com>; Sun, 8 Sep 2019 18:08:32 -0700 (PDT)
Received: from out-15.smtp.github.com (out-15.smtp.github.com [192.30.254.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 370BF12004D for <quic-issues@ietf.org>; Sun, 8 Sep 2019 18:08:32 -0700 (PDT)
Date: Sun, 08 Sep 2019 18:08:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1567991311; bh=ruZ1y3rjRYhZ9Vuwplu+rd2HwXdPpNthqCVHydX4PM4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z4aPVASBBFFsppZaGGRdV5VvKb/fcpfMHF6uZ7aB5D19b5HBHYne3HEf/PjyP65h4 3BPCzCQHvqbEQoauxxASf4EaS1cUgXY5V7cJ/RXlNzsqN/5SM4iZPu1qqfmfLqv8QN b1wDet/L4FngL9H8a80nXy4SREobKTFmGqJ9coVE=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYTZZD43O56E4ULHIV3QLFH7EVBNHHB2OXHYQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3009/review/285247588@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3009@github.com>
References: <quicwg/base-drafts/pull/3009@github.com>
Subject: Re: [quicwg/base-drafts] Cache git repo, draft references in Circle (#3009)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d75a60f5c6d9_214e3fddfc2cd96c2407b3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/OTLNqvQd5jYPEkJzUDYIC9KEB10>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 01:08:34 -0000

martinthomson commented on this pull request.

I was concerned that this wouldn't be very much good.

The `{{ .Revision }}` key means that that cache entry is only going to be good for rebuilding that revision, something that we don't do, except when we are tagging a release.  The tag for `{{ .Branch }}` is probably good, but not for `master`, which will be baking in as soon as this lands (if it hasn't already).

The `{{ epoch }}` tag is only good if we run builds within a second of each other.

How about an idea that I just had.  We can run arbitrary code to generate a file.  If we were to write something to a file and then use `{{ checksum ".reference-cache-key" }}` we could ensure that the value rolls over daily so that we have a hot reference cache.  We could do the same for the git cache so that it is mostly at most a certain date old.  You can even cascade caches by reading from `{{ checksum ".cache-today" }}` and `{{ checksum ".cache-yesterday" }}`.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3009#pullrequestreview-285247588