Re: [codesprints] Errors from GitHub CI tools
Jim Fenton <fenton@bluepopcorn.net> Tue, 07 June 2022 20:18 UTC
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: codesprints@ietfa.amsl.com
Delivered-To: codesprints@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0B5C15948C for <codesprints@ietfa.amsl.com>; Tue, 7 Jun 2022 13:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqczRNwau_hM for <codesprints@ietfa.amsl.com>; Tue, 7 Jun 2022 13:18:29 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96888C14F727 for <codesprints@ietf.org>; Tue, 7 Jun 2022 13:18:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7evuilRAN6PiWaysmM8HwBLRUlex0jbhIKFEp86lk/M=; b=eh6BaT1Qi1NWu55q+m34P3iKHo D3oktv+eoomZVN8Rk1m2Zc39owki6bMWjeRAdvB9Dwqt0bWV3G5zKFgx/CPoA+I9J1sARV6mS7D7R YCw++KOzx3lnfqsdTvEFJ2epkWaICTw27rn7J2j0w8qIcss2nTyLNHmrkZU5E+Xl/KJE=;
Received: from [64.71.6.2] (helo=[10.100.11.204]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1nyfel-0000un-Gc; Tue, 07 Jun 2022 13:18:27 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Jennifer Richards <jennifer@painless-security.com>
Cc: codesprints@ietf.org
Date: Tue, 07 Jun 2022 13:18:26 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <174993FC-D49E-4F78-A59E-8389B66E97D8@bluepopcorn.net>
In-Reply-To: <97bfef2f-e095-40ba-5021-c7129c25bf04@painless-security.com>
References: <7F866EE3-4F20-43C7-AF29-858222C9A054@bluepopcorn.net> <97bfef2f-e095-40ba-5021-c7129c25bf04@painless-security.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/H-jFsMH1iNBhXGUCqNjF6yuE5nY>
Subject: Re: [codesprints] Errors from GitHub CI tools
X-BeenThere: codesprints@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "List for coordinating \(and following up on\) codesprint activities" <codesprints.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/codesprints>, <mailto:codesprints-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/codesprints/>
List-Post: <mailto:codesprints@ietf.org>
List-Help: <mailto:codesprints-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/codesprints>, <mailto:codesprints-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2022 20:18:34 -0000
Thanks, Jennifer! That was exactly what I was looking for. -Jim On 7 Jun 2022, at 12:30, Jennifer Richards wrote: > Hi Jim, > >> >> Having done that, I get email from GitHub every day or so to tell me >> that building the nightly dev DB image has failed. Should this be >> fixed, or is there a way to turn off the CI stuff on my fork? >> > > If you go to the Settings tab, under Actions -> General heading you can "Disable Actions". This will turn off all the CI actions. > > jennifer
- [codesprints] Errors from GitHub CI tools Jim Fenton
- Re: [codesprints] Errors from GitHub CI tools Salz, Rich
- Re: [codesprints] Errors from GitHub CI tools Jennifer Richards
- Re: [codesprints] Errors from GitHub CI tools Jim Fenton