Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-25 Thread Tobias Frost
Am Sonntag, den 25.09.2016, 00:08 -0400 schrieb Yaroslav Halchenko:
> On Sun, 25 Sep 2016, Santiago Vila wrote:
> 
> > 
> > On Sun, Sep 25, 2016 at 01:14:16AM +0200, Tobias Frost wrote:
> 
> > 
> > > 
> > > I'd then NMU it tomorrow,,,
> 
> > 
> > I would skip this package, as I think the maintainer is around and
> > not MIA.
> 
> NMUs are welcome if you see a clear workaround (force setting up some
> TERM so tests pass?)
> 
> 
Thanks for the head up, Yaroslav!

--
tobi



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Yaroslav Halchenko

On Sun, 25 Sep 2016, Santiago Vila wrote:

> On Sun, Sep 25, 2016 at 01:14:16AM +0200, Tobias Frost wrote:

> > I'd then NMU it tomorrow,,,

> I would skip this package, as I think the maintainer is around and not MIA.

NMUs are welcome if you see a clear workaround (force setting up some
TERM so tests pass?)


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Santiago Vila
On Sun, Sep 25, 2016 at 01:14:16AM +0200, Tobias Frost wrote:

> At the moment I cannot install sbuild due to the perl breakage...

Oh, that's why I like running testing (not unstable).

> But I think it is not necessary as you confirmed the issue is enough
> for me. 
> Can you try to apply the patch from #798296 to see if it builds?

Yes, it fixes the build when TERM is not set.

BTW: I've just discovered that running sbuild by hand makes TERM to be
inherited from my own bash session. I had to unset TERM to check that.

(The build logs I attached are created by sbuild as a child process
of cron, so that's why TERM is not set in such case).

> I'd then NMU it tomorrow,,,

I would skip this package, as I think the maintainer is around and not MIA.

> Greetings from the Salzburg BSP,

Good luck.

Thanks.



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Tobias Frost
Am Sonntag, den 25.09.2016, 00:13 +0200 schrieb Santiago Vila:
> severity 802191 serious
> thanks
> 
> While reviewing unreproducible FTBFS bugs I found this one,
> which I can reproduce without any problem at all and it's
> not random at all.
> 
> I attach five different build logs from four different autobuilders,
> using sbuild.
> 
> I think downgrading a bug just because it does not happen with
> pbuilder is just wrong, because the official buildds use sbuild,
> not pbuilder (hence I'm raising to serious again).
> 
> If the TERM thing is an essential difference between pbuilder and
> sbuild, please consider filing a bug against pbuilder for that.
> 
> Tobias, could you please try with sbuild? In case you could still
> not reproduce this with sbuild, please contact me privately, maybe
> I can lend you a virtual machine as a last resort.

At the moment I cannot install sbuild due to the perl breakage...
But I think it is not necessary as you confirmed the issue is enough
for me. 
Can you try to apply the patch from #798296 to see if it builds?
I'd then NMU it tomorrow,,,


Greetings from the Salzburg BSP,

tobi



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Santiago Vila
I said:
> the official buildds use sbuild,

Just in case anybody want to argue that "this package does not need to
build in the official buildds because it's Arch: all".

Well, yes, it needs to be buildable in the "Arch: all" autobuilder
as well. That's precisely what release goal in Bug #830997 is about.
We should be able to upload every package in stretch in source only
form, and it should work.

Thanks.



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Santiago Vila
severity 802191 serious
thanks

While reviewing unreproducible FTBFS bugs I found this one,
which I can reproduce without any problem at all and it's
not random at all.

I attach five different build logs from four different autobuilders,
using sbuild.

I think downgrading a bug just because it does not happen with
pbuilder is just wrong, because the official buildds use sbuild,
not pbuilder (hence I'm raising to serious again).

If the TERM thing is an essential difference between pbuilder and
sbuild, please consider filing a bug against pbuilder for that.

Tobias, could you please try with sbuild? In case you could still
not reproduce this with sbuild, please contact me privately, maybe
I can lend you a virtual machine as a last resort.

Thanks.

bats_0.4.0-1_amd64-20160924T213546Z.gz
Description: application/gzip


bats_0.4.0-1_amd64-20160924T213559Z.gz
Description: application/gzip


bats_0.4.0-1_amd64-20160924T213603Z.gz
Description: application/gzip


bats_0.4.0-1_amd64-20160924T213606Z.gz
Description: application/gzip


bats_0.4.0-1_amd64-20160924T213608Z.gz
Description: application/gzip


Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2016-09-24 Thread Tobias Frost
Control: severity -1 important

I also reproduce this FTBFS in a sid pbuilder enviorment when provoking
an unset TERM:

diff -Naur bats-0.4.0-orig/debian/rules bats-0.4.0/debian/rules
--- bats-0.4.0-orig/debian/rules2014-12-07 06:53:16.0
+0100
+++ bats-0.4.0/debian/rules 2016-09-24 22:23:13.569025103 +0200
@@ -3,6 +3,8 @@
 # output every command that modifies files on the build system.
 #DH_VERBOSE = 1
 
+undefine TERM
+
 # main packaging script based on dh7 syntax
 %:
dh $@

However I cannot reproduce it in a sid pbuilder, so I downgrade this
bug.

--
tobi

On Sun, 18 Oct 2015 09:08:37 +0100 "Chris West (Faux)"  wrote:
> Source: bats
> Version: 0.4.0-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[1]: Entering directory '/bats-0.4.0'
> bin/bats --tap test
> 1..43
> ok 1 no arguments prints usage instructions
> ok 2 -v and --version print version number
> ok 3 -h and --help print help
> ok 4 invalid filename prints an error
> ok 5 empty test file runs zero tests
> ok 6 one passing test
> not ok 7 summary passing tests
> # (in test file test/bats.bats, line 46)
> #   `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
> not ok 8 summary passing and skipping tests
> # (in test file test/bats.bats, line 52)
> #   `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
> not ok 9 summary passing and failing tests
> # (in test file test/bats.bats, line 58)
> #   `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
> not ok 10 summary passing, failing and skipping tests
> # (in test file test/bats.bats, line 64)
> #   `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
> ok 11 one failing test
> ok 12 one failing and one passing test
> 
> 
> 
> debian/rules:14: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 1
> make[1]: Leaving directory '/bats-0.4.0'
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/bats.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> 



Bug#802191: bats: FTBFS: not ok 7 summary passing tests

2015-10-18 Thread Chris West (Faux)
Source: bats
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Entering directory '/bats-0.4.0'
bin/bats --tap test
1..43
ok 1 no arguments prints usage instructions
ok 2 -v and --version print version number
ok 3 -h and --help print help
ok 4 invalid filename prints an error
ok 5 empty test file runs zero tests
ok 6 one passing test
not ok 7 summary passing tests
# (in test file test/bats.bats, line 46)
#   `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
not ok 8 summary passing and skipping tests
# (in test file test/bats.bats, line 52)
#   `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
not ok 9 summary passing and failing tests
# (in test file test/bats.bats, line 58)
#   `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
not ok 10 summary passing, failing and skipping tests
# (in test file test/bats.bats, line 64)
#   `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
ok 11 one failing test
ok 12 one failing and one passing test



debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/bats-0.4.0'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/bats.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)