On June 20, 2022 2:04 PM, I wrote: >To: 'Junio C Hamano' <gitster@xxxxxxxxx> >Cc: git@xxxxxxxxxxxxxxx >Subject: Test Failure t5510,t5562 - was RE: [ANNOUNCE] Git v2.37.0-rc1 > >Subtests t5510.69, 71, 97, 99, 125, 127, 147, 149, 151, 153, 155, 157, 159, 161, 163, >165, 167, 170 failed in rc1 on the NonStop ia64 platform. These were working in rc0, >but after analysis, I do not think that is relevant. Here is what we see for subtest >69: > >expecting success of 5510.69 'link prune fetch.prune=unset >remote.origin.prune=unset fetch.pruneTags=unset >remote.origin.pruneTags=unset --prune origin refs/tags/*:refs/tags/*; >branch:kept tag:pruned': >... > git fetch >"file:///home/jenkins/.jenkins/workspace/Git_Pipeline@2/t/trash >directory.t5510-fetch/." "+refs/heads/*:refs/remotes/origin/*" && ... > git$git_fetch_c fetch --prune >"file:///home/jenkins/.jenkins/workspace/Git_Pipeline/t/trash directory.t5510- >fetch/." refs/tags/*:refs/tags/* && > >What seems to be happening is that the test script is computing the wrong parent >directory in the second case, cutting the @2. We use Jenkins for our builds and >occasional multiple builds run. The @2 is Jenkins way of running in another place. >This seems to be confusing the script parsing of the parent, causing the issue. >When I rebuilt and test in the primary directory, the failures disappeared because >no @2. > >t5562 also seems to have the same issue. A more complete list of tests failing in path with @2 is - and this is likely caused by different constructs: t5300, t5510, t5516, t5562, t5601, t7528.
