IETF Logo Mail Archive

Re: [codesprints] CI errors on datatracker fork

Jim Fenton <fenton@bluepopcorn.net> Mon, 03 April 2023 18:51 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 73AE9C1526FB for <codesprints@ietfa.amsl.com>; Mon, 3 Apr 2023 11:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 0nUWGfx38q-h for <codesprints@ietfa.amsl.com>; Mon, 3 Apr 2023 11:51:09 -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 C3BD3C1524C8 for <codesprints@ietf.org>; Mon, 3 Apr 2023 11:51:09 -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=EZ8HAITs/1lXPEbwuuiITOobfHfybvqYuMTaNwmstzA=; b=utwDt2CByy5Fpm1rny9gDNtrEi wAm0Y9clMfgKaIRxJcUbUhuUfTn07z/wdxL1AuJKt1DJjqfElriYzBN+4rfPc07XC2o/0uosxwRRS ZZ77f0OutDcDyW+hj+jzfJH+sQPYTcl9DURW59a5AporSwpz/wav422itlPdWuI7Wh2Y=;
Received: from [2601:647:4400:4781:edc0:2da:17d9:69b0] (helo=[10.10.20.192]) 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 1pjPGi-0007U6-Vz; Mon, 03 Apr 2023 11:51:07 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
To: Jennifer Richards <jennifer@painless-security.com>
Cc: codesprints@ietf.org
Date: Mon, 03 Apr 2023 11:51:02 -0700
X-Mailer: MailMate (1.14r5852)
Message-ID: <7E398086-0661-4B8C-8186-8A7D4E0B4C39@bluepopcorn.net>
In-Reply-To: <06270206-4369-f6d5-1e45-9706ae3db166@painless-security.com>
References: <5AA8CE52-F964-4EE1-95C9-1DB26B2F80A6@bluepopcorn.net> <06270206-4369-f6d5-1e45-9706ae3db166@painless-security.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/codesprints/f3IxiyL0zvEOT1NYVc8vVg_wwJk>
Subject: Re: [codesprints] CI errors on datatracker fork
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: Mon, 03 Apr 2023 18:51:14 -0000

Thanks, Jennifer. That’s exactly what I was looking for.

-Jim

On 3 Apr 2023, at 11:24, Jennifer Richards wrote:

> Hi Jim,
>
> On 4/3/23 3:18 PM, Jim Fenton wrote:
>> I’m not familiar at all with how CI works in GitHub. Is there a setting somewhere that I can put in my fork that says, “don’t do CI”? Or should this actually be working?
>>
>
> You likely have actions enabled on your fork. If you're using the GitHub UI, go to Settings -> Actions -> General and be sure "Actions permissions" is set to "Disable actions".
>
> If it's already disabled, then we'll have to try something else...
>
> jennifer

v2.23.0 | Report a Bug | By Email