git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>, "'Junio C Hamano'" <gitster@pobox.com>
Subject: RE: [BUG] Git 2.42.0-rc2 t1092.57 script error
Date: Fri, 18 Aug 2023 19:25:51 -0400	[thread overview]
Message-ID: <01b801d9d22b$5781eea0$0685cbe0$@nexbridge.com> (raw)
In-Reply-To: <202308182302.37IN2tgW2384518@secure.elehost.com>

><mailto:rsbecker@nexbridge.com> writes:
>>On Friday, August 18, 2023 5:28 PM, Junio C Hamano wrote:
>><mailto:rsbecker@nexbridge.com> writes:
>>
>>> Is this new test code? The local qualified appears to be a bash
>>> extension, not available across all shells - from what I can
>>> determine. Is it really required here or just fancy?
>>
>>You are asking a wrong person ;-)
>>
>>You know Git well enough to run "git blame" on this code yourself to answer
the first
>>question and find out whom to ask it:
>>
>>  https://github.com/git/git/blame/master/t/test-lib-functions.sh#L1794

>Code has been around 2 years. I will chase this down with the platform
>vendor.

Well, it was investigated. local is not the issue. It is working correctly on ksh and bash on the platform. It is looking like the issue was something in the environment. We are on a new test system that is seriously overloaded, so it is possible that we ran out of resources or were close to the limit when the test started - multiple times earlier in the day, but it is feeling much better now and the subtest passed.

I'm going to write this one off as no factor.

Thanks for the help.
--Randall


      parent reply	other threads:[~2023-08-18 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 17:47 [BUG] Git 2.42.0-rc2 t1092.57 script error rsbecker
2023-08-18 19:05 ` Junio C Hamano
2023-08-18 19:38   ` rsbecker
2023-08-18 21:27     ` Junio C Hamano
2023-08-18 21:53       ` rsbecker
     [not found]         ` <202308182302.37IN2tgW2384518@secure.elehost.com>
2023-08-18 23:25           ` rsbecker [this message]

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='01b801d9d22b$5781eea0$0685cbe0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).