Control: fixed -1 0.35-1
Hi,
Andrey Rahmatullin wrote:
> On Sun, Mar 31, 2013 at 12:54:32PM +0100, Dominic Hargreaves wrote:
> > > FWIW it didn't fail here in a sid am64 chroot.
> >
> > True; in sid, the failure (with 0.15-1) seems to come at
> >
> > # Failed test 'errstr'
> > # at t/020-low_level_client.t line 125.
> > # 'Duplicate key exists in unique index 0'
> > # doesn't match '(?^:already exists)'
> >
> > (i386 and amd64).
> Oh, I also missed the fact that the bug has a different version that I
> tested.
> So, to be clear, I tested 0.35-1 which is the sid version.
> 0.15-1 from testing on a sid amd64 chroot fails with the same error as in
> your quote above.
I can reproduce the issue on a Sid machine (no chroot) with 0.15-1 on
i386 Sid + Experimental:
ok 25 - type
not ok 26 - errstr
ok 27 - * select reply code
However, 0.35-1 from sid FTBFS for me, too, on i386 Sid + Experimental:
Test Summary Report
-------------------
t/020-low_level_client.t (Wstat: 256 Tests: 9 Failed: 1)
Failed test: 9
Non-zero exit status: 1
Parse errors: Bad plan. You planned 101 tests but ran 9.
t/050-async-client.t (Wstat: 256 Tests: 10 Failed: 1)
Failed test: 10
Non-zero exit status: 1
Parse errors: Bad plan. You planned 80 tests but ran 10.
t/060-sync-client.t (Wstat: 28416 Tests: 9 Failed: 0)
Non-zero exit status: 111
Parse errors: Bad plan. You planned 57 tests but ran 9.
t/080-tarantool.t (Wstat: 28416 Tests: 9 Failed: 0)
Non-zero exit status: 111
Parse errors: Bad plan. You planned 33 tests but ran 9.
t/090-parallel-requests.t (Wstat: 256 Tests: 12 Failed: 1)
Failed test: 12
Non-zero exit status: 1
Parse errors: Bad plan. You planned 49 tests but ran 12.
t/100-transform.t (Wstat: 28416 Tests: 11 Failed: 0)
Non-zero exit status: 111
Parse errors: Bad plan. You planned 18 tests but ran 11.
t/110-netsplit-readahead.t (Wstat: 256 Tests: 12 Failed: 1)
Failed test: 12
Non-zero exit status: 1
Parse errors: Bad plan. You planned 24 tests but ran 12.
Files=16, Tests=581, 8 wallclock secs ( 0.53 usr 0.07 sys + 6.64 cusr 0.90
csys = 8.14 CPU)
Result: FAIL
Failed 7/16 test programs. 4/581 subtests failed.
Yeah, no clean chroot, lots of perl modules installed, but anyway. I
actually just tried to quickly reproduce the "0.15-1 FTBFS but 0.35-1
works" statement to mark 0.35-1 as "fixed", but actually there seems to
be at least some FTBFS issues, too.
So next step is pbuilder (on amd64 though). And it actually builds
fine, hence marking 0.35-1 as fixed. I'll try to figure out which
other package caused the above mentioned FTBFS and file it as a
separate (non-RC) bug.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
