Bug#373892: git-core: FTBFS: tests failure
tags 373892 + unreproducible quit On Fri, Jun 16, 2006 at 09:23:02AM +0200, Julien Danjou wrote: > There was a problem while autobuilding your package: > > > Automatic build of git-core_1.3.3-2 on avidan by sbuild/i386 0.46 > > Build started at 20060616-0523 > > ** Hi Julien, I cannot reproduce this, neither on a current sid/i386 system, nor with pbuilder. Also there's an (I guess) autobuilt binary package for i386 already available through http://ftp.debian.org/debian/pool/main/g/git-core/ although no logs are available through buildd.debian.org. Can you please retry, and if it again fails, post the complete log? Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373892: git-core: FTBFS: tests failure
tags 373892 - unreproducible severity 373892 important retitle 373892 git-core: FTBFS: selftests fail with /bin/sh->dash quit On Fri, Jun 16, 2006 at 09:23:02AM +0200, Julien Danjou wrote: > There was a problem while autobuilding your package: > > > Automatic build of git-core_1.3.3-2 on avidan by sbuild/i386 0.46 > > Build started at 20060616-0523 > > ** Ok, looks like /bin/sh is linked to dash on avidan, that makes the selftests fail as you reported. Thanks, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#373892: git-core: FTBFS: tests failure
Processing commands for [EMAIL PROTECTED]: > tags 373892 - unreproducible Bug#373892: git-core: FTBFS: tests failure Tags were: unreproducible Tags removed: unreproducible > severity 373892 important Bug#373892: git-core: FTBFS: tests failure Severity set to `important' from `serious' > retitle 373892 git-core: FTBFS: selftests fail with /bin/sh->dash Bug#373892: git-core: FTBFS: tests failure Changed Bug title. > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#373892: git-core: FTBFS: tests failure
Processing commands for [EMAIL PROTECTED]: > tags 373892 + unreproducible Bug#373892: git-core: FTBFS: tests failure There were no tags set. Tags added: unreproducible > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373892: git-core: FTBFS: tests failure
Package: git-core Version: 1.3.3-2 Severity: serious Hello, There was a problem while autobuilding your package: > Automatic build of git-core_1.3.3-2 on avidan by sbuild/i386 0.46 > Build started at 20060616-0523 > ** ... > /usr/bin/make -C t/ all > make[2]: Entering directory `/build/buildd/git-core-1.3.3/t' > *** t-basic.sh *** > * ok 1: .git/objects should be empty after git-init-db in an empty repo. > * ok 2: .git/objects should have 3 subdirectories. > * ok 3: git-update-index without --add should fail adding. > * ok 4: git-update-index with --add should succeed. > * ok 5: writing tree out with git-write-tree > * ok 6: validate object ID of a known tree. > * ok 7: git-update-index without --remove should fail removing. > * ok 8: git-update-index with --remove should be able to remove. > * ok 9: git-write-tree should be able to write an empty tree. > * ok 10: validate object ID of a known tree. > * ok 11: adding various types of objects with git-update-index --add. > * ok 12: showing stage with git-ls-files --stage > * ok 13: validate git-ls-files output for a known tree. > * ok 14: writing tree out with git-write-tree. > * ok 15: validate object ID for a known tree. > * ok 16: showing tree with git-ls-tree > * ok 17: git-ls-tree output for a known tree. > * ok 18: showing tree with git-ls-tree -r > * ok 19: git-ls-tree -r output for a known tree. > * ok 20: git-read-tree followed by write-tree should be idempotent. > * ok 21: validate git-diff-files output for a know cache/work tree state. > * ok 22: git-update-index --refresh should succeed. > * ok 23: no diff after checkout and git-update-index --refresh. > * passed all 23 test(s) > *** t0010-racy-git.sh *** > * ok 1: Racy GIT trial #0 part A > * ok 2: Racy GIT trial #0 part B > * ok 3: Racy GIT trial #1 part A > * ok 4: Racy GIT trial #1 part B > * ok 5: Racy GIT trial #2 part A > * ok 6: Racy GIT trial #2 part B > * ok 7: Racy GIT trial #3 part A > * ok 8: Racy GIT trial #3 part B > * ok 9: Racy GIT trial #4 part A > * ok 10: Racy GIT trial #4 part B > * passed all 10 test(s) > *** t1000-read-tree-m-3way.sh *** > * ok 1: adding test file NN and Z/NN > * ok 2: adding test file ND and Z/ND > * ok 3: adding test file NM and Z/NM > * ok 4: adding test file DN and Z/DN > * ok 5: adding test file DD and Z/DD > * ok 6: adding test file DM and Z/DM > * ok 7: adding test file MN and Z/MN > * ok 8: adding test file MD and Z/MD > * ok 9: adding test file MM and Z/MM > * ok 10: adding test file SS > * ok 11: adding test file TT > * ok 12: prepare initial tree > * ok 13: change in branch A (removal) > * ok 14: change in branch A (modification) > * ok 15: change in branch A (modification) > * ok 16: change in branch A (modification) > * ok 17: change in branch A (modification) > * ok 18: change in branch A (modification) > * ok 19: change in branch A (modification) > * ok 20: change in branch A (addition) > * ok 21: change in branch A (addition) > * ok 22: change in branch A (addition) > * ok 23: change in branch A (addition) > * ok 24: change in branch A (addition) > * ok 25: change in branch A (edit) > * ok 26: change in branch A (change file to directory) > * ok 27: recording branch A tree > * ok 28: reading original tree and checking out > * ok 29: change in branch B (removal) > * ok 30: change in branch B (modification) > * ok 31: change in branch B (modification) > * ok 32: change in branch B (modification) > * ok 33: change in branch B (modification) > * ok 34: change in branch B (modification) > * ok 35: change in branch B (modification) > * ok 36: change in branch B (addition) > * ok 37: change in branch B (addition) > * ok 38: change in branch B (addition) > * ok 39: change in branch B (addition) > * ok 40: change in branch B (addition and modification) > * ok 41: change in branch B (modification) > * ok 42: change in branch B (addition of a file to conflict with directory) > * ok 43: recording branch B tree > * ok 44: keep contents of 3 trees for easy access > * ok 45: 3-way merge with git-read-tree -m, empty cache > * ok 46: 3-way merge with git-read-tree -m, match H > * ok 47: 1 - must not have an entry not in A. > * ok 48: 2 - must match B in !O && !A && B case. > * ok 49: 2 - matching B alone is OK in !O && !A && B case. > * ok 50: 3 - must match A in !O && A && !B case. > * ok 51: 3 - matching A alone is OK in !O && A && !B case. > * ok 52: 3 (fail) - must match A in !O && A && !B case. > * ok 53: 4 - must match and be up-to-date in !O && A && B && A!=B case. > * ok 54: 4 (fail) - must match and be up-to-date in !O && A && B && A!=B > case. > * ok 55: 4 (fail) - must match and be up-to-date in !O && A && B && A!=B > case. > * ok 56: 5 - must match in !O && A && B && A==B case. > * ok
