Skip to contentSkip to conversation

t7300-clean.sh fails "not ok 32 - should avoid cleaning possible submodules" on debian jessie

DISCUSSION Pirate Praveen 3 participants 7 messages Jun 16, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this error (tests upto this succeeds).

not ok 32 - should avoid cleaning possible submodules

I added debian stretch repo to apt sources.list and ran apt-get source -b git.

You can see the build options passed here
http://repo.or.cz/git/debian.git/blob/HEAD:/debian/rules

Since it is a working fine on debian sid/unstable, I did not want to report it to debian package maintainers.

I noticed the same failure for git 2.8.0-rc3 as well. I could ignore the test failure and go ahead, but I'd like to fix this if possible.

Thanks
Praveen

#1 lore raw

Hi Pirate Praveen,

Quoted 4 lines · Pirate Praveen

I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this error (tests upto this succeeds).

not ok 32 - should avoid cleaning possible submodules

How about re-running the script with -i -v -x? If the output is still not shining enough light on it, maybe you want to paste the (relevant part of the) output into a reply?

Ciao,
Johannes

#2 lore raw
Quoted 4 lines · Johannes Schindelin

Hi Pirate Praveen,

On Tue, 7 Jun 2016, Pirate Praveen wrote:

Quoted 8 lines
Quoted 4 lines

I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this error (tests upto this succeeds).

not ok 32 - should avoid cleaning possible submodules

How about re-running the script with -i -v -x? If the output is still not shining enough light on it, maybe you want to paste the (relevant part of the) output into a reply?

+ rm -fr to_clean possible_sub1
+ mkdir to_clean possible_sub1
+ test_when_finished rm -rf possible_sub*
+ test 0 = 0
+ test_cleanup={ rm -rf possible_sub*

                } && (exit "$eval_ret"); eval_ret=$?; :

+ echo gitdir: foo
+
+ chmod 0 possible_sub1/.git
+
+ git clean -f -d
Skipping repository baz/boo

Skipping repository foo/
Removing possible_sub1/
Skipping repository repo/
Skipping repository sub2/
Removing to_clean/
+ test_path_is_file possible_sub1/.git
+ test -f possible_sub1/.git
+ echo File possible_sub1/.git doesn't exist. File possible_sub1/.git doesn't exist.
+ false
error: last command exited with $?=1
not ok 32 - should avoid cleaning possible submodules #

#               rm -fr to_clean possible_sub1 &&
#               mkdir to_clean possible_sub1 &&
#               test_when_finished "rm -rf possible_sub*" &&
#               echo "gitdir: foo" >possible_sub1/.git &&
#               >possible_sub1/hello.world &&
#               chmod 0 possible_sub1/.git &&
#               >to_clean/should_clean.this &&
#               git clean -f -d &&
#               test_path_is_file possible_sub1/.git &&
#               test_path_is_file possible_sub1/hello.world &&
#               test_path_is_missing to_clean

#

Quoted 3 lines

Ciao,
Johannes

#4 lore raw
Quoted 1 line · Stefan Beller

(Are you telling me that patch is faulty?)

The patch is not part of v2.8.1 but part of v2.8.3, so take a later version, or cherry-pick that patch manually.

#5 lore raw
Quoted 6 lines · Stefan Beller
Quoted 1 line · Stefan Beller

(Are you telling me that patch is faulty?)

The patch is not part of v2.8.1 but part of v2.8.3, so take a later version, or cherry-pick that patch manually.

Thanks! I have ignored that test failure for now. Good to know its fixed in 2.8.3.

#6 lore raw
In reply to Pirate Praveen

Hi Pirate Praveen,

Quoted 8 lines · Pirate Praveen
Quoted 7 lines · Johannes Schindelin

Hi Pirate Praveen,

Quoted 3 lines · Pirate Praveen

I'm trying to rebuild git 2.8.1 on debian jessie/stable and I get this error (tests upto this succeeds).

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

not ok 32 - should avoid cleaning possible submodules

How about re-running the script with -i -v -x? If the output is still not shining enough light on it, maybe you want to paste the (relevant part of the) output into a reply?

+ rm -fr to_clean possible_sub1
[...]

Sorry, I must have missed your diligent analysis.

Ciao,
Johannes