On Mon, Oct 03, 2011 at 03:59:50AM -0500, Jonathan Nieder wrote:
> Petr Salinger wrote:
>
> > It effectively test return code of
> >
> >fprintf (fp, "%2147483648d%2147483648d", 1, 1);
> >
> > The printf family returns int and should return number of written bytes.
> > It therefore cannot excee
- ret = fprintf (fp, "%" SN "d%" SN "d", 1, 1);
+ ret = fprintf (fp, "%" SN "d%" SN "d%" SN "d", 1, 1);
It have to be changed into
fprintf (fp, "%" SN "d%" SN "d%" SN "d", 1, 1, 1);
or
fprintf (fp, "%" SN "d%" SN "d%" SN "d", 1, 2, 3);
+ ret = fprintf (fp, "%" SN "d", 1, 1);
And
Petr Salinger wrote:
> It effectively test return code of
>
>fprintf (fp, "%2147483648d%2147483648d", 1, 1);
>
> The printf family returns int and should return number of written bytes.
> It therefore cannot exceed MAX_INT.
>
> But the test tries to print twice entry with width MAX_INT+1.
> I
I looked more into.
In fact I do not understand what the test tries to test.
It effectively test return code of
fprintf (fp, "%2147483648d%2147483648d", 1, 1);
The printf family returns int and should return number of written bytes.
It therefore cannot exceed MAX_INT.
But the test tries to
2011/10/2 Robert Millan :
> OTOH, running it from command-line results in:
>
> Timed out: killed the child process
More specifically, it is sitting on waitpid() call (line 341).
Could this be related to #639658 ?
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.de
2011/10/2 Robert Millan :
> 2011/10/1 Jonathan Nieder :
>> Robert Millan wrote:
>>
>>> Encountered regressions that don't match expected failures:
>>> bug22.out, Error 1
>>
>> And what is the content of bug22.out?
>
> Empty file.
OTOH, running it from command-line results in:
Timed out: killed th
2011/10/2 Petr Salinger :
> What is your CPU ?
>
> It happens also on my PC (in 32 bit pass), with
> Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
(note: running kfreebsd-i386 as a VirtualBox guest)
--
Robert Millan
--
To UNSUBSCRIBE, email to de
2011/10/2 Aurelien Jarno :
> bug22 basically tries to write /dev/null. Is /dev correctly mounted on
> your system?
Yes.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
2011/10/1 Jonathan Nieder :
> Robert Millan wrote:
>
>> Encountered regressions that don't match expected failures:
>> bug22.out, Error 1
>
> And what is the content of bug22.out?
Empty file.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subjec
Encountered regressions that don't match expected failures:
bug22.out, Error 1
What is your CPU ?
It happens also on my PC (in 32 bit pass), with
Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
Petr
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsu
tag 644023 + unreproducible
thanks
On Sat, Oct 01, 2011 at 10:56:03PM +0200, Robert Millan wrote:
> Package: eglibc
> Version: 2.13-21
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
>
> >From build log:
>
> #
> # Testsuite failures, someone should be working towards
> # fixing these! T
Robert Millan wrote:
> Encountered regressions that don't match expected failures:
> bug22.out, Error 1
And what is the content of bug22.out?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: eglibc
Version: 2.13-21
User: debian-...@lists.debian.org
Usertags: kfreebsd
>From build log:
#
# Testsuite failures, someone should be working towards
# fixing these! They are listed here for the purpose of
# regression testing during builds.
# Format: , Error [(ignored)]
#
annexc.out,
13 matches
Mail list logo
