{"thread":{"id":"60124","subject":"[BUG] Git 2.42.0-rc2 t1092.57 script error","startedAt":"2023-08-18T17:49:03Z","lastAt":"2023-08-18T23:26:59Z","messageCount":6,"participants":["rsbecker@nexbridge.com","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"480782","messageId":"018601d9d1fc$2049ede0$60ddc9a0$@nexbridge.com","threadId":"60124","inReplyTo":null,"subject":"[BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-18T17:47:52Z","receivedAt":"2023-08-18T17:49:03Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"Hi Team,\n\nI'm getting the following error when running t1092.57 in Git 2.42.0-rc2 on\nNonStop ia64:\n\n+ ensure_not_expanded status\ntest_region[8]: test: argument expected\ngrep: ensure_full_index: No such file or directory\nerror: last command exited with $?=1\nnot ok 57 - sparse-index is not expanded\n\nAny suggestions?\n\nThanks,\nRandall\n--\nBrief whoami: NonStop&UNIX developer since approximately\nUNIX(421664400)\nNonStop(211288444200000000)\n-- In real life, I talk too much.\n\n\n\n"},{"id":"480785","messageId":"xmqqedk0uq6r.fsf@gitster.g","threadId":"60124","inReplyTo":"018601d9d1fc$2049ede0$60ddc9a0$@nexbridge.com","subject":"Re: [BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-18T19:05:16Z","receivedAt":"2023-08-18T19:05:58Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"<rsbecker@nexbridge.com> writes:\n\n> I'm getting the following error when running t1092.57 in Git 2.42.0-rc2\n> on NonStop ia64:\n>\n> + ensure_not_expanded status\n> test_region[8]: test: argument expected\n> grep: ensure_full_index: No such file or directory\n> error: last command exited with $?=1\n> not ok 57 - sparse-index is not expanded\n>\n> Any suggestions?\n\nSorry for not coming up with anything concrete.\n\n\"ensure_not_expanded status\" should be running as its second step\n\n\ttest_region ! index ensure_full_index trace2.txt\n\nWhich should do this:\n\n    test_region () {\n            local expect_exit=0\n            if test \"$1\" = \"!\"\n            then\n                    expect_exit=1\n                    shift\n            fi\n\n            grep -e\t'\"region_enter\".*\"category\":\"'\"$1\"'\",\"label\":\"'\"$2\"\\\" \"$3\"\n            exitcode=$?\n\n            if test $exitcode != $expect_exit\n            then\n\n\nAs \"grep\" complains that ensure_full_index is not a file, when the\ncommand runs there the file name is \"$3\".\n\nSo it appears to me that the first \n\n\ttest \"$1\" = \"!\"\n\nis not firing and failing to set expect_exit to 1 and shift the \"!\"\nout of $@.  Why?  I dunno.  Perhaps your shell has quirks around\n\"local\"?  I dunno.\n\n\n"},{"id":"480787","messageId":"01a101d9d20b$836f1a30$8a4d4e90$@nexbridge.com","threadId":"60124","inReplyTo":"xmqqedk0uq6r.fsf@gitster.g","subject":"RE: [BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-18T19:38:01Z","receivedAt":"2023-08-18T19:39:11Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 18, 2023 3:05 PM, Junio C Hamano wrote:\n><rsbecker@nexbridge.com> writes:\n>\n>> I'm getting the following error when running t1092.57 in Git\n>> 2.42.0-rc2 on NonStop ia64:\n>>\n>> + ensure_not_expanded status\n>> test_region[8]: test: argument expected\n>> grep: ensure_full_index: No such file or directory\n>> error: last command exited with $?=1\n>> not ok 57 - sparse-index is not expanded\n>>\n>> Any suggestions?\n>\n>Sorry for not coming up with anything concrete.\n>\n>\"ensure_not_expanded status\" should be running as its second step\n>\n>\ttest_region ! index ensure_full_index trace2.txt\n>\n>Which should do this:\n>\n>    test_region () {\n>            local expect_exit=0\n>            if test \"$1\" = \"!\"\n>            then\n>                    expect_exit=1\n>                    shift\n>            fi\n>\n>            grep -e\n'\"region_enter\".*\"category\":\"'\"$1\"'\",\"label\":\"'\"$2\"\\\" \"$3\"\n>            exitcode=$?\n>\n>            if test $exitcode != $expect_exit\n>            then\n>\n>\n>As \"grep\" complains that ensure_full_index is not a file, when the command\nruns\n>there the file name is \"$3\".\n>\n>So it appears to me that the first\n>\n>\ttest \"$1\" = \"!\"\n>\n>is not firing and failing to set expect_exit to 1 and shift the \"!\"\n>out of $@.  Why?  I dunno.  Perhaps your shell has quirks around \"local\"?\nI dunno.\n\nIs this new test code? The local qualified appears to be a bash extension,\nnot available across all shells - from what I can determine. Is it really\nrequired here or just fancy?\n\n"},{"id":"480790","messageId":"xmqqzg2ot50w.fsf@gitster.g","threadId":"60124","inReplyTo":"01a101d9d20b$836f1a30$8a4d4e90$@nexbridge.com","subject":"Re: [BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-08-18T21:27:43Z","receivedAt":"2023-08-18T21:28:54Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"<rsbecker@nexbridge.com> writes:\n\n> Is this new test code? The local qualified appears to be a bash extension,\n> not available across all shells - from what I can determine. Is it really\n> required here or just fancy?\n\nYou are asking a wrong person ;-)\n\nYou know Git well enough to run \"git blame\" on this code yourself to\nanswer the first question and find out whom to ask it:\n\n  https://github.com/git/git/blame/master/t/test-lib-functions.sh#L1794\n\n"},{"id":"480792","messageId":"01b301d9d21e$81c7ff40$8557fdc0$@nexbridge.com","threadId":"60124","inReplyTo":"xmqqzg2ot50w.fsf@gitster.g","subject":"RE: [BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-18T21:53:58Z","receivedAt":"2023-08-18T21:54:58Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On Friday, August 18, 2023 5:28 PM, Junio C Hamano wrote:\n><rsbecker@nexbridge.com> writes:\n>\n>> Is this new test code? The local qualified appears to be a bash\n>> extension, not available across all shells - from what I can\n>> determine. Is it really required here or just fancy?\n>\n>You are asking a wrong person ;-)\n>\n>You know Git well enough to run \"git blame\" on this code yourself to answer\nthe first\n>question and find out whom to ask it:\n>\n>  https://github.com/git/git/blame/master/t/test-lib-functions.sh#L1794\n\nCode has been around 2 years. I will chase this down with the platform\nvendor.\nThanks\n\n\n"},{"id":"480793","messageId":"01b801d9d22b$5781eea0$0685cbe0$@nexbridge.com","threadId":"60124","inReplyTo":"202308182302.37IN2tgW2384518@secure.elehost.com","subject":"RE: [BUG] Git 2.42.0-rc2 t1092.57 script error","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2023-08-18T23:25:51Z","receivedAt":"2023-08-18T23:26:59Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"><mailto:rsbecker@nexbridge.com> writes:\n>>On Friday, August 18, 2023 5:28 PM, Junio C Hamano wrote:\n>><mailto:rsbecker@nexbridge.com> writes:\n>>\n>>> Is this new test code? The local qualified appears to be a bash\n>>> extension, not available across all shells - from what I can\n>>> determine. Is it really required here or just fancy?\n>>\n>>You are asking a wrong person ;-)\n>>\n>>You know Git well enough to run \"git blame\" on this code yourself to answer\nthe first\n>>question and find out whom to ask it:\n>>\n>>  https://github.com/git/git/blame/master/t/test-lib-functions.sh#L1794\n\n>Code has been around 2 years. I will chase this down with the platform\n>vendor.\n\nWell, 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.\n\nI'm going to write this one off as no factor.\n\nThanks for the help.\n--Randall\n\n"}]}