Your message dated Wed, 17 Feb 2010 04:30:52 -0600
with message-id <20100217103052.gb6...@progeny.tock>
and subject line Re: [FTBFS] t7400-submodule-basic.sh fails
has caused the Debian Bug report #569594,
regarding git-core: [FTBFS] t7400-submodule-basic.sh fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
569594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-core
Version: 1:1.6.6.2-1
Severity: serious
Justification: FTBFS
Apparently re-enabling the git test suite (see #568915) reveals
another problem on the ia64. The test is in submodule support, so it
is probably worth disabling for the moment (since the rest of git
should be usable). What is most odd is that v1.6.6 built by hand on
merulo did not reveal the same problem.
The failed test:
test_expect_success 'update --init' '
mv init init2 &&
git config -f .gitmodules submodule.example.url "$(pwd)/init2" &&
git config --remove-section submodule.example
git submodule update init > update.out &&
grep "not initialized" update.out &&
test ! -d init/.git &&
git submodule update --init init &&
test -d init/.git
'
Difference in output from my local i386 (please ignore the hunk
header) [1]:
| @@ -323,11 +69715,19 @@ warning: unable to remove submodule init
| test -d init/.git
|
|
| -Submodule path 'init' not initialized
| -Submodule 'example' (<top>/t/trash directory.t7400-submodule-basic/init2)
registered for path 'init'
| -Initialized empty Git repository in <top>/t/trash
directory.t7400-submodule-basic/init/.git/
| -Submodule path 'init': checked out 'OBJID'
| -* ok 24: update --init
| +* FAIL 24: update --init
| +
| +
| + mv init init2 &&
| + git config -f .gitmodules submodule.example.url "$(pwd)/init2"
&&
| + git config --remove-section submodule.example
| + git submodule update init > update.out &&
| + grep "not initialized" update.out &&
| + test ! -d init/.git &&
| + git submodule update --init init &&
| + test -d init/.git
| +
| +
|
| * expecting success:
The remainder of t7400-submodule-basic.sh worked fine. I do not know
if any later tests would have failed, too.
With git 1.6.6 on merulo before the libc memchr fix, this did _not_
show up: although many other tests failed, t7400-submodule-basic.sh
had worked fine. [2]
To learn more, you can run sh t7400-submodule-basic.sh -v from the t/
subdirectory of a git build directory and look at the files in
"trash directory.t7400-submodule-basic". I would love to do so myself.
Any ia64 admins willing to provide access for debugging purposes?
Thoughts?
Jonathan
[1] Build log:
https://buildd.debian.org/fetch.cgi?pkg=git-core&arch=ia64&ver=1:1.6.6.2-1&stamp=1265994466&file=log&as=raw
[2] Build by hand of v1.6.6:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=37;bug=563882
--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:
> The failed test:
>
> test_expect_success 'update --init' '
All the affected platforms took to 1.7.0 without problems, though no
relevant change happened upstream. I suspect some part of the
toolchain (sbuild? binutils?) was broken. I’d still love to know what
happened, but that is only for academic reasons, so closing.
--- End Message ---
