git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [BUG] Git 2.42.0-rc2 t1092.57 script error
@ 2023-08-18 17:47 rsbecker
  2023-08-18 19:05 ` Junio C Hamano
  0 siblings, 1 reply; 6+ messages in thread
From: rsbecker @ 2023-08-18 17:47 UTC (permalink / raw)
  To: git

Hi Team,

I'm getting the following error when running t1092.57 in Git 2.42.0-rc2 on
NonStop ia64:

+ ensure_not_expanded status
test_region[8]: test: argument expected
grep: ensure_full_index: No such file or directory
error: last command exited with $?=1
not ok 57 - sparse-index is not expanded

Any suggestions?

Thanks,
Randall
--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [BUG] Git 2.42.0-rc2 t1092.57 script error
  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
  0 siblings, 1 reply; 6+ messages in thread
From: Junio C Hamano @ 2023-08-18 19:05 UTC (permalink / raw)
  To: rsbecker; +Cc: git

<rsbecker@nexbridge.com> writes:

> I'm getting the following error when running t1092.57 in Git 2.42.0-rc2
> on NonStop ia64:
>
> + ensure_not_expanded status
> test_region[8]: test: argument expected
> grep: ensure_full_index: No such file or directory
> error: last command exited with $?=1
> not ok 57 - sparse-index is not expanded
>
> Any suggestions?

Sorry for not coming up with anything concrete.

"ensure_not_expanded status" should be running as its second step

	test_region ! index ensure_full_index trace2.txt

Which should do this:

    test_region () {
            local expect_exit=0
            if test "$1" = "!"
            then
                    expect_exit=1
                    shift
            fi

            grep -e	'"region_enter".*"category":"'"$1"'","label":"'"$2"\" "$3"
            exitcode=$?

            if test $exitcode != $expect_exit
            then


As "grep" complains that ensure_full_index is not a file, when the
command runs there the file name is "$3".

So it appears to me that the first 

	test "$1" = "!"

is not firing and failing to set expect_exit to 1 and shift the "!"
out of $@.  Why?  I dunno.  Perhaps your shell has quirks around
"local"?  I dunno.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: [BUG] Git 2.42.0-rc2 t1092.57 script error
  2023-08-18 19:05 ` Junio C Hamano
@ 2023-08-18 19:38   ` rsbecker
  2023-08-18 21:27     ` Junio C Hamano
  0 siblings, 1 reply; 6+ messages in thread
From: rsbecker @ 2023-08-18 19:38 UTC (permalink / raw)
  To: 'Junio C Hamano'; +Cc: git

On Friday, August 18, 2023 3:05 PM, Junio C Hamano wrote:
><rsbecker@nexbridge.com> writes:
>
>> I'm getting the following error when running t1092.57 in Git
>> 2.42.0-rc2 on NonStop ia64:
>>
>> + ensure_not_expanded status
>> test_region[8]: test: argument expected
>> grep: ensure_full_index: No such file or directory
>> error: last command exited with $?=1
>> not ok 57 - sparse-index is not expanded
>>
>> Any suggestions?
>
>Sorry for not coming up with anything concrete.
>
>"ensure_not_expanded status" should be running as its second step
>
>	test_region ! index ensure_full_index trace2.txt
>
>Which should do this:
>
>    test_region () {
>            local expect_exit=0
>            if test "$1" = "!"
>            then
>                    expect_exit=1
>                    shift
>            fi
>
>            grep -e
'"region_enter".*"category":"'"$1"'","label":"'"$2"\" "$3"
>            exitcode=$?
>
>            if test $exitcode != $expect_exit
>            then
>
>
>As "grep" complains that ensure_full_index is not a file, when the command
runs
>there the file name is "$3".
>
>So it appears to me that the first
>
>	test "$1" = "!"
>
>is not firing and failing to set expect_exit to 1 and shift the "!"
>out of $@.  Why?  I dunno.  Perhaps your shell has quirks around "local"?
I dunno.

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?


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [BUG] Git 2.42.0-rc2 t1092.57 script error
  2023-08-18 19:38   ` rsbecker
@ 2023-08-18 21:27     ` Junio C Hamano
  2023-08-18 21:53       ` rsbecker
  0 siblings, 1 reply; 6+ messages in thread
From: Junio C Hamano @ 2023-08-18 21:27 UTC (permalink / raw)
  To: rsbecker; +Cc: git

<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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: [BUG] Git 2.42.0-rc2 t1092.57 script error
  2023-08-18 21:27     ` Junio C Hamano
@ 2023-08-18 21:53       ` rsbecker
       [not found]         ` <202308182302.37IN2tgW2384518@secure.elehost.com>
  0 siblings, 1 reply; 6+ messages in thread
From: rsbecker @ 2023-08-18 21:53 UTC (permalink / raw)
  To: 'Junio C Hamano'; +Cc: git

On Friday, August 18, 2023 5:28 PM, Junio C Hamano wrote:
><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.
Thanks



^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: [BUG] Git 2.42.0-rc2 t1092.57 script error
       [not found]         ` <202308182302.37IN2tgW2384518@secure.elehost.com>
@ 2023-08-18 23:25           ` rsbecker
  0 siblings, 0 replies; 6+ messages in thread
From: rsbecker @ 2023-08-18 23:25 UTC (permalink / raw)
  To: git, 'Junio C Hamano'

><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


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-08-18 23:26 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).