From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 672A0C433EF for ; Thu, 14 Jul 2022 02:10:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230399AbiGNCK6 convert rfc822-to-8bit (ORCPT ); Wed, 13 Jul 2022 22:10:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229441AbiGNCK5 (ORCPT ); Wed, 13 Jul 2022 22:10:57 -0400 Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 427772BEE; Wed, 13 Jul 2022 19:10:56 -0700 (PDT) Received: from Mazikeen (cpe00fc8d49d843-cm00fc8d49d840.cpe.net.cable.rogers.com [174.119.96.21] (may be forged)) (authenticated bits=0) by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 26E2AkUH048754 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jul 2022 22:10:46 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) Reply-To: From: To: , "'Junio C Hamano'" , Cc: "'Linux Kernel'" , References: <01af01d896b1$a48e32f0$edaa98d0$@nexbridge.com> <01b101d896c4$31761bd0$94625370$@nexbridge.com> In-Reply-To: <01b101d896c4$31761bd0$94625370$@nexbridge.com> Subject: RE: [Test Failures] Git v2.37.1 (was RE: [ANNOUNCE] Git v2.37.1 and others) Date: Wed, 13 Jul 2022 22:10:39 -0400 Organization: Nexbridge Inc. Message-ID: <021701d89726$ed4d09b0$c7e71d10$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Mailer: Microsoft Outlook 16.0 Content-Language: en-ca Thread-Index: AQOax8rq/kYLSctl3duwOPHxjLu0zAJkQfEUAKRaJqep4HjDUA== Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On July 13, 2022 10:24 AM, I wrote: >On July 13, 2022 8:11 AM, I wrote: >>On July 12, 2022 1:07 PM, Junio C Hamano wrote: >>>Git v2.37.1, together with v2.30.5, v2.31.4, v2.32.3, v2.33.4, >>>v2.34.4, v2.35.4, and >>>v2.36.2 for older maintenance tracks, are now available at the usual places. >>> >>>These are to address CVE-2022-29187, where the fixes in v2.36.1 and >>>below to address CVE-2022-24765 released earlier may not have been >complete. >> >>Following are net new test failures with 2.37.1 compared with 2.37.0 >>are as follows on NonStop ia64 and x86 platforms: >> >>t5516-fetch-push subtests 53, 113 >> >>t5545-push-options subtest 9 > >Test passes when not run in Jenkins CI/CD > >>t5601-clone subtest 8 > >Test passes when not run in Jenkins CI/CD > >>t7502-commit-porcelain subtests 20-26, 29-33, 42-47 > >Test passes when not run in Jenkins CI/CD > >>t7528-signed-commit-ssh subtests 4, 5 > >Test passes when not run in Jenkins CI/CD > >So it looks like a Jenkins/git test interaction is the issue here. I'm wondering >whether running the test with /dev/null might make a >difference when running in Jenkins. The tty where Jenkins was started is in a >permanently disconnected state. > >Mostly ignore the subtest failures, but still, would like to know why these subtests >in particular. Strangely, setting stdin to /dev/null and stderr to /dev/null makes no difference in the test results. stdout is the Jenkins pipe, which is Java of course, but roughly a popen(x, "r"). I have no explanation at this point why specific tests fail - other than OpenSSH, which I know attempts to prompt if it thinks the tty is even remotely reasonable.