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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id A0AF61F910 for ; Thu, 24 Nov 2022 09:17:14 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="X3gRUvO0"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229815AbiKXJQF (ORCPT ); Thu, 24 Nov 2022 04:16:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229730AbiKXJQE (ORCPT ); Thu, 24 Nov 2022 04:16:04 -0500 Received: from mail-oa1-x29.google.com (mail-oa1-x29.google.com [IPv6:2001:4860:4864:20::29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B05F114493 for ; Thu, 24 Nov 2022 01:16:03 -0800 (PST) Received: by mail-oa1-x29.google.com with SMTP id 586e51a60fabf-12c8312131fso1354396fac.4 for ; Thu, 24 Nov 2022 01:16:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nLu/m6Y8BOl+DRvEgh8qafBxdGNvRwB677z5A39tgOg=; b=X3gRUvO03tZNuDWNXTSEZ5viq3w0EPG6w/SKZtVUqvUjqlcXW+leD5FUtuvdUPcO6g DmjH2xAPheGQQ6PGZi0dXBPSZLqXUoUYNoKTJX1fNq8Uo9NNTmvCsqUyrTuyl5DS4xWA N9bC3yHA1/1dNiS9xLLDwKmiIRwaDzIMaU2xmLPoK/DH5ZUJmjXTyJvy+A1XH3ztMK2h ZEQo+EY2ZlDLvGzaJjFr4ePqZq4HjNBNryL2C58KlCypnUnvsb/Llbg/ZL75pZapKi1b tLgYUs65QplUNdGg7jpsCRKAGt+vKjAtp2JqFX/f6tYguSVXqFcz7lvmnzpG2cXP6ubG 6ihw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nLu/m6Y8BOl+DRvEgh8qafBxdGNvRwB677z5A39tgOg=; b=c9zSysvuhuiT61q9yTfP9CN+N93K2PhNT7XKOCYc4Xm+H8hWJEYIa6C0LsCHmCFBjY Ja72fwfP5bVriS4OrTv7qn4n7RNq/xVybhHIJMNAvpBbCRTXo+vVZjQQSR2h1ELkEAnH YODCd9by7NPleFwXVpdeLI3jVqcHCDZpHCVdbcar1WJaaH4sB3r6dmRxeOHauvTmfGJV RSDqnyZGBdTDRbVccs0hYRurEk9yyk71yMtYmCXsB7VJ6UKZzbOuu2h+imBGKatPQ0xP zwz1YF/jOlE/rePrL5B1xi3BOfxH8mWKY5pZF8liUrRCbRkdZ+3hYpI0nk0osuiaC8Ks GNFg== X-Gm-Message-State: ANoB5pn8244s6r0+vz10CCkv02kFGdNr0ojR96f3vRZ7bZMpGobYLwGN nUhcF5k/+UTpNAfT4BUVS4rWlgWf/2RYZ+BFEIo= X-Google-Smtp-Source: AA0mqf4rvj9wyLOACm6xc1rZ1+SQWgLrLng2nlrzWB/0a3WGo0X6niTAwmwT1nRRHihYBjKSlrX1MeUJqGub6kicVnY= X-Received: by 2002:a05:6870:d994:b0:13d:9ace:3376 with SMTP id gn20-20020a056870d99400b0013d9ace3376mr20602209oab.251.1669281362887; Thu, 24 Nov 2022 01:16:02 -0800 (PST) MIME-Version: 1.0 References: <20221123150233.13039-1-worldhello.net@gmail.com> <20221123150233.13039-3-worldhello.net@gmail.com> In-Reply-To: From: Jiang Xin Date: Thu, 24 Nov 2022 17:15:51 +0800 Message-ID: Subject: Re: [PATCH 2/2] ci: upgrade version of p4 To: Johannes Schindelin Cc: Git List , Junio C Hamano , Jiang Xin Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Nov 24, 2022 at 4:16 PM Johannes Schindelin wrote: > > From: Jiang Xin > > > > There would be a segmentation fault when running p4 v16.2 on ubuntu > > 22.04 which is the latest version of ubuntu runner image for github > > actions. Upgrade p4 from version 16.2 to 19.2 will fix this issue. > > I was about to embark on a debugging session when I had the splendid idea > to look at the Git mailing list archives to see whether anybody else had > encountered that particular problem. > > However, when I pushed a branch with this fix, it still segfaulted even > when downloading version 19.2 (link: > https://github.com/dscho/git/actions/runs/3538788474/jobs/5939977231#step:3:387): Yes, p4d 19.2 also has segfault errors, and p4 version 21.x and above is OK. Maybe yesterday I only check p4, and forgot to check p4d by hands. It is fixed in v2 by upgrade p4 to 21.2. -- Jiang Xin