From: <rsbecker@nexbridge.com>
To: "'SZEDER Gábor'" <szeder.dev@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: [BUGS] Git v2.51.2 on NonStop
Date: Wed, 29 Oct 2025 18:41:27 -0400 [thread overview]
Message-ID: <000201dc4925$2cdbc450$86934cf0$@nexbridge.com> (raw)
In-Reply-To: <aQKVByfUdYHSEcDz@szeder.dev>
On October 29, 2025 6:28 PM, SZEDER Gábor wrote:
>On Tue, Oct 28, 2025 at 01:40:42PM -0400, rsbecker@nexbridge.com wrote:
>> I have found new defects on 2.51.2 that were not present in 2.51.1 when building
>with OpenSSL 3.5 (probably unrelated).
>>
>> Many failures in t7900 resulting from the use of test_subcommand ! as seen
>below. This is run in bash 5.0.18:
>>
>> + test_subcommand git gc --quiet --no-detach --skip-foreground-tasks
>> + 0< run-no-auto.txt
>> {"event":"child_start","sid":"20251028T172435.690328Z-H36b1c598-P7b000
>> 02d","thread":"main","time":"2025-10-28T17:24:35.879833Z","file":"/hom
>> e/jenkinsbuild/.jenkins/workspace/Git_Pipeline/run-command.c","line":7
>> 40,"child_id":2,"child_class":"?","use_shell":false,"argv":["git","gc"
>> ,"--quiet","--no-detach","--skip-foreground-tasks"]}
>> + test_subcommand ! git gc --auto --quiet --no-detach
>> + --skip-foreground-tasks 0< run-auto.txt
>> test_subcommand[5]: test: argument expected
>
>This is a strange trace output, as it includes file descriptor redirections, but lacks the
>trace of commands executed in test_subcommands. This trace doesn't look like it's
>coming from Bash.
The test_subcommand[5]: test: argument expect is coming from bash. I cannot see how
it is coming from anywhere else. The test was run with -x but snipped. Reference to
test_subcommand ! git... fails exactly the same way. Is there something else I can provide?
next prev parent reply other threads:[~2025-10-29 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 15:56 [ANNOUNCE] Git v2.51.2 Junio C Hamano
2025-10-28 17:40 ` [BUGS] Git v2.51.2 on NonStop rsbecker
2025-10-29 22:28 ` SZEDER Gábor
2025-10-29 22:41 ` rsbecker [this message]
2025-10-29 23:18 ` SZEDER Gábor
2025-10-30 0:24 ` rsbecker
2025-10-30 2:53 ` Jeff King
2025-10-30 13:52 ` D. Ben Knoble
2025-10-30 14:59 ` rsbecker
2025-10-30 21:23 ` brian m. carlson
2025-10-30 15:15 ` Kristoffer Haugsbakk
2025-10-30 16:02 ` rsbecker
2025-10-30 19:42 ` Junio C Hamano
2025-10-30 20:25 ` Kristoffer Haugsbakk
2025-10-30 21:46 ` [BUGS] Git v2.51.2 on NonStop5 rsbecker
2025-10-30 22:30 ` SZEDER Gábor
2025-10-31 1:02 ` rsbecker
2025-10-31 14:09 ` rsbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000201dc4925$2cdbc450$86934cf0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).