forwarded 563882 http://sourceware.org/bugzilla/show_bug.cgi?id=11230
thanks
Hi Aurelian,
Aurelien Jarno wrote:
On Tue, Jan 26, 2010 at 04:06:32PM -0600, Jonathan Nieder wrote:
FYI: http://sourceware.org/bugzilla/show_bug.cgi?id=10162
Maybe glibc 2.11.1 (which includes a cherry-pick of
On 2010-01-26 Jonathan Nieder jrnie...@gmail.com wrote:
Andreas Metzler wrote:
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ M.out
/tmp/GIT/git-core-1.6.6-debug/git-is-binary M.out 4.out
static buffer is not binary
stdin is not binary
M.out
reassign 563882 libc6.1 2.10.2-5
severity 563882 critical
retitle 563882 ia64: mmap reading null bytes that should not be there
thanks
Hi libc maintainers,
mmap() on ia64 seems to be totally broken. git does something
like the following to detect binary files:
struct stat st;
severity 563882 important
retitle 563882 ia64: memchr overshots
thanks
On Tue, Jan 26, 2010 at 01:48:34PM -0600, Jonathan Nieder wrote:
severity 563882 critical
Please explain. git is neither unrelated to glibc nor does this cause
serious data loss.
That is, it maps the file into memory and
Bastian Blank wrote:
On Tue, Jan 26, 2010 at 01:48:34PM -0600, Jonathan Nieder wrote:
severity 563882 critical
Please explain. git is neither unrelated to glibc nor does this cause
serious data loss.
My mistake, sorry about that.
The test program does not properly show what is going on.
Bastian Blank wrote:
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
| lstat(argv[1], st);
|
| int fd = open(argv[1], O_RDONLY);
| void *data =
On Tue, Jan 26, 2010 at 04:06:32PM -0600, Jonathan Nieder wrote:
Bastian Blank wrote:
The following program shows the cause:
| #include sys/stat.h
| #include sys/mman.h
| #include fcntl.h
|
| int main(int argc, const char * const argv[])
| {
| struct stat st;
|
Hi again,
Andreas Metzler wrote:
ametz...@merulo:/tmp/GIT/git-core-1.6.6-debug/t/trash
directory.t1001-read-tree-m-2way$ M.out
/tmp/GIT/git-core-1.6.6-debug/git-is-binary M.out 4.out
static buffer is not binary
stdin is not binary
M.out is binary
4.out is not binary
I’ve also
Jonathan Nieder wrote:
I have attached
generic-is-binary.c to pin this down; could you try:
uname -r
dpkg -l libc6
gcc -Wall -W -O -o generic-is-binary generic-is-binary.c
M.out ./generic-is-binary M.out
If M.out (but not stdin) is reported to be binary, great:
Subject: debian/rules: ignore test suite failures on ia64
Even git versions that previously passed the test suite no longer
pass the test suite on merulo or mundy (text files are detected
to be binary, causing many tests using git diff to break).
Probably some basic component like libc or the
On 2010-01-25 Jonathan Nieder jrnie...@gmail.com wrote:
Andreas Metzler wrote:
[...]
Binary files a/M.out and b/4.out differ
Hi Andreas and ia64 porters,
If you find time, could you save the is-binary.c in the git source
tree and try
make git-is-binary
M.out ./git-is-binary
On 2010-01-22 Jonathan Nieder jrnie...@gmail.com wrote:
Anders Kaseorg wrote:
Now that Git 1.6.6.1 is out, I propose we build git-core 1.6.6.1-1 with
the patch I posted above http://bugs.debian.org/563882#10, which lets
the two tests in question expect to fail on ia64 only.
From the
On 2010-01-09 Jonathan Nieder jrnie...@gmail.com wrote:
[...]
Instead, it appears that
git diff --no-index M.out 4.out 4diff.out
is not writing the output it should. To test this hypothesis, it
would be nice to use a copy of git built with DEB_BUILD_OPTIONS=nocheck
to compare
-- % --
Hello,
Andreas Metzler wrote:
$ /tmp/GIT/git-core-1.6.6/git diff --no-index M.out 4.out
diff --git a/M.out b/4.out
index 4aefa95..d5ec90a 100644
Binary files a/M.out and b/4.out differ
$ cat M.out
100644 346d4e61f111336a1443ef6b2e834aa5b1a7f91a 0 bozbar
100644
Andreas Metzler wrote:
On 2010-01-09 Jonathan Nieder jrnie...@gmail.com wrote:
-- % -- M.out
100644 346d4e61f111336a1443ef6b2e834aa5b1a7f91a 0bozbar
100644 8e4020bb5a8d8c873b25de15933e75cc0fc275df 0frotz
100644 dca6b92303befc93086aa025d90a5facd7eb2812 0nitfol
-- % --
with
--
tags 563882 +patch
thanks
On Sat, 9 Jan 2010, Jonathan Nieder wrote:
To test this hypothesis, it would be nice to use a copy of git built
with DEB_BUILD_OPTIONS=nocheck to compare
[…]
Thanks for looking at this, Jonathan.
Now that Git 1.6.6.1 is out, I propose we build git-core 1.6.6.1-1
Hi Anders,
Thanks for your work on this.
Anders Kaseorg wrote:
Now that Git 1.6.6.1 is out, I propose we build git-core 1.6.6.1-1 with
the patch I posted above http://bugs.debian.org/563882#10, which lets
the two tests in question expect to fail on ia64 only.
From the log, it looks like
Hi Itanium porters,
The git test suite is failing on mundy. Any ideas about why?
(Or about how to try to investigate this --- a good emulator? machine
access? a willing guinea pig who can try patches?)
Some details on the test failure follow.
Anders Kaseorg wrote:
Some time between 1.6.5-1
Jonathan Nieder wrote:
So far so good, as the read_tree_twoway output reveals:
| 100644 346d4e61f111336a1443ef6b2e834aa5b1a7f91a 0 bozbar
| 100644 8e4020bb5a8d8c873b25de15933e75cc0fc275df 0 frotz
| 100644 dca6b92303befc93086aa025d90a5facd7eb2812 0 nitfol
| 100644
Package: git-core
Version: 1:1.6.5.2-1
Severity: serious
Justification: FTBFS
Some time between 1.6.5-1 and 1.6.5.2-1, git-core started failing to build
on ia64, because the test t1001-read-tree-m-2way.sh is failing. This has
continued in every version up through 1.6.6-1.
The same bug was
I tried to set up an emulated ia64 chroot with which to track down the
problem, but apparently ski doesn’t work http://bugs.debian.org/563890.
:-(
Looking at build logs from various versions, it is always the same two
tests that fail, and only on ia64. Most users aren’t on ia64, and it
21 matches
Mail list logo
