Acknowledgement sent
to Mattia Rizzolo <mattia@mapreri.org>:
New Bug report received and forwarded. Copy sent to qa-jenkins-dev@lists.alioth.debian.org, reproducible-builds@lists.alioth.debian.org, Yann Dirson <dirson@debian.org>.
(Mon, 15 Jun 2015 17:48:05 GMT) (full text, mbox, link).
Package: cssc
Version: 1.4.0-3
Dear maintainer,
cssc suddenly started to FTBFS in jenkins.debian.net, in the context of
reproducble builds testing.
This is weird because the previous version used to build fine.
The first time a FTBFS was encountered is with the 1.4.0-2 in testing only
(while on unstable it built fine).
Anyway 1.4.0-3 hangs as follow:
=======================
get/t-option.sh:tc1...passed
get/t-option.sh:oddstart-0...passed
get/t-option.sh:oddstart-1...passed
get/t-option.sh:oddstart-2...passed
get/t-option.sh:oddstart-3...passed
get/t-option.sh:oddstart-4...passed
All Tests in /tmp/buildd/cssc-1.4.0/tests/get/t-option.sh are now completed on tools in '/tmp/buildd/cssc-1.4.0/src'
PASS t-option.sh:
Running test /tmp/buildd/cssc-1.4.0/tests/get/writable.sh
Directory under test is /tmp/buildd/cssc-1.4.0/src
get/writable.sh:W1...passed
get/writable.sh:W2...passed
get/writable.sh:W3...passed
get/writable.sh:W4...passed
W5...passed
get/writable.sh:W6...passed
W7...passed
All Tests in /tmp/buildd/cssc-1.4.0/tests/get/writable.sh are now completed on tools in '/tmp/buildd/cssc-1.4.0/src'
PASS writable.sh:
==========================
To see the full build log, check
https://jenkins.debian.net/view/reproducible/job/reproducible_builder_theta/15582/consoleFull
This is the last build log on unstable, the very same happened in testing with
the same version and on unstable some days ago (but thinking of a temporary
issue we just ignore it).
The package builds fine on my laptop too, hance keeping this bug as
severity:normal, please do feel free do either downgrade or upgrade the severity
at your opinion.
Similar FTBFS in the past where due to being high parallelized, as we build with
DEB_BUILD_OPTIONS="parallel=23", maybe this is the case too, I don't know.
We are willing to help investigating the issue, and we welcome your help too.
PS. In the meantime we blacklisted the package from the testing for
reproducibly.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 19 Jun 2015 19:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Yann Dirson <ydirson@free.fr>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 19 Jun 2015 19:21:04 GMT) (full text, mbox, link).
To: Mattia Rizzolo <mattia@mapreri.org>, 788863@bugs.debian.org
Cc: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the tests
Date: Fri, 19 Jun 2015 21:16:23 +0200
Hello,
Can you look at the process tree under the test run, and possibly get
a look at what the leaf processes are doing ?
I'd think that the testsuite is probably not thought for a parallel
make it looks hard to predict anything. Maybe I should arrange so
that dh_auto_test does not run in parallel - probably adding
--max-parallel=1 to its invocation would do the trick.
Can you get it rerun with this and see if it improves something ?
Best regards,
--
Yann
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 19 Jun 2015 19:21:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Yann Dirson <ydirson@free.fr>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 19 Jun 2015 19:21:08 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 19 Jun 2015 23:06:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Mattia Rizzolo <mattia@mapreri.org>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 19 Jun 2015 23:06:03 GMT) (full text, mbox, link).
Subject: Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the tests
Date: Fri, 19 Jun 2015 23:03:21 +0000
On Fri, Jun 19, 2015 at 7:16 PM, Yann Dirson <ydirson@free.fr> wrote:
> Can you look at the process tree under the test run, and possibly get
> a look at what the leaf processes are doing ?
can you tell me more precisely what i should do? run the build and?
> I'd think that the testsuite is probably not thought for a parallel
> make it looks hard to predict anything. Maybe I should arrange so
> that dh_auto_test does not run in parallel - probably adding
> --max-parallel=1 to its invocation would do the trick.
>
> Can you get it rerun with this and see if it improves something ?
well, if you upload it i can just unblacklist it and schedule it for a
regular build.
--
regards,
Mattia Rizzolo
GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapreri
Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Wed, 24 Jun 2015 22:03:08 GMT) (full text, mbox, link).
Acknowledgement sent
to Yann Dirson <ydirson@free.fr>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Wed, 24 Jun 2015 22:03:08 GMT) (full text, mbox, link).
To: Mattia Rizzolo <mattia@mapreri.org>, 788863@bugs.debian.org
Subject: Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the tests
Date: Thu, 25 Jun 2015 00:01:06 +0200
On Fri, Jun 19, 2015 at 11:03:21PM +0000, Mattia Rizzolo wrote:
> On Fri, Jun 19, 2015 at 7:16 PM, Yann Dirson <ydirson@free.fr> wrote:
> > Can you look at the process tree under the test run, and possibly get
> > a look at what the leaf processes are doing ?
>
> can you tell me more precisely what i should do? run the build and?
When it gets stuck, I'd use something like "pstree -p $(pidof
debuild)" to get an idea of what's still running. If it's a test, "ps
l" should tell us which one it is, and with some luck we'll be able to
see the problem by just looking at that particular test. If that's
not sufficient, I'd go with "strace -p" first.
> > I'd think that the testsuite is probably not thought for a parallel
> > make it looks hard to predict anything. Maybe I should arrange so
> > that dh_auto_test does not run in parallel - probably adding
> > --max-parallel=1 to its invocation would do the trick.
> >
> > Can you get it rerun with this and see if it improves something ?
>
> well, if you upload it i can just unblacklist it and schedule it for a
> regular build.
OK, I'll do that later this week. Won't that make it more
difficult/time-consuming for you to get the information with the
current version if I upload a new one too soon ?
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Wed, 24 Jun 2015 22:33:07 GMT) (full text, mbox, link).
Acknowledgement sent
to Mattia Rizzolo <mattia@mapreri.org>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Wed, 24 Jun 2015 22:33:07 GMT) (full text, mbox, link).
On Thu, Jun 25, 2015 at 12:01:06AM +0200, Yann Dirson wrote:
> On Fri, Jun 19, 2015 at 11:03:21PM +0000, Mattia Rizzolo wrote:
> > On Fri, Jun 19, 2015 at 7:16 PM, Yann Dirson <ydirson@free.fr> wrote:
> > > Can you look at the process tree under the test run, and possibly get
> > > a look at what the leaf processes are doing ?
> >
> > can you tell me more precisely what i should do? run the build and?
>
> When it gets stuck, I'd use something like "pstree -p $(pidof
> debuild)" to get an idea of what's still running. If it's a test, "ps
> l" should tell us which one it is, and with some luck we'll be able to
> see the problem by just looking at that particular test. If that's
> not sufficient, I'd go with "strace -p" first.
just manually ran a build on the host the very same way the job does and it
went good. Dunno maybe this is trigger also by a particulr load, and a load of
~60 is not enough (and it's too much, who knows..).
FTR it took 6:16 minutes.
> > > I'd think that the testsuite is probably not thought for a parallel
> > > make it looks hard to predict anything. Maybe I should arrange so
> > > that dh_auto_test does not run in parallel - probably adding
> > > --max-parallel=1 to its invocation would do the trick.
> > >
> > > Can you get it rerun with this and see if it improves something ?
> >
> > well, if you upload it i can just unblacklist it and schedule it for a
> > regular build.
>
> OK, I'll do that later this week. Won't that make it more
> difficult/time-consuming for you to get the information with the
> current version if I upload a new one too soon ?
Not sure I get your question.
If you upload a "fixed" (as in: it can't fail anymore, but that's enough for me,
i don't think so many people run with -j 23) package I can just
unblacklisted it and forget about it.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Source: cssc
Source-Version: 1.4.0-4
We believe that the bug you reported is fixed in the latest version of
cssc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 788863@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yann Dirson <dirson@debian.org> (supplier of updated cssc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 25 Jun 2015 23:12:27 +0200
Source: cssc
Binary: cssc
Architecture: source amd64
Version: 1.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson <dirson@debian.org>
Changed-By: Yann Dirson <dirson@debian.org>
Description:
cssc - Clone of the Unix SCCS revision-control system
Closes: 788863
Changes:
cssc (1.4.0-4) unstable; urgency=medium
.
* Make sure autopkgtest runs the "initial" test first
* Set --max-parallel=1 on dh_auto_test to avoid potentially unforeseen
races (Closes: #788863).
Checksums-Sha1:
3e109b174ccd305a518f4ffbd9b370f6449083ea 1842 cssc_1.4.0-4.dsc
6dc7347fe0ddfcab45d51387c1d6a417a6b52144 9196 cssc_1.4.0-4.debian.tar.xz
df3ccb87b6e5c966739b7bd5df96fb87e0937d69 447898 cssc_1.4.0-4_amd64.deb
Checksums-Sha256:
ae813d72e68fce143b647c9eaeb13223a02af1893b2a75d62681e8db832fd983 1842 cssc_1.4.0-4.dsc
71489068d70e6f472fb4d9f586d378f63edecdaae2bb29b37b921714d67caae2 9196 cssc_1.4.0-4.debian.tar.xz
87d378d7e58462806b84a278f4efd22351b3c4057682147705a12332cad22f66 447898 cssc_1.4.0-4_amd64.deb
Files:
4dafdffe31f8f054dd9f2d07b5f0c74b 1842 vcs extra cssc_1.4.0-4.dsc
ddad14e617817b8676c6f90613156427 9196 vcs extra cssc_1.4.0-4.debian.tar.xz
0b0dba195e386d9dae83071c088525ba 447898 vcs extra cssc_1.4.0-4_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIVAwUBVYxxNQ2F8pYlo/n9AQjTiQ//QafkcJnMy/jRIQXYYzp1/w9qHSDBa5o6
nuOFHNTHtNOwGG/MP7CVSLx0mJaOe+2bI/YiW372xlcsaf6kw2YVjLzqDlJDe1QZ
z/E+W0di+Z/oLL5BDsnaqaeDXkVbS8+MWepf8cFVMRCdU1c0IUPDlHmU3fmCnDgb
atSjERf5ftuWitKwUx1E2c/6sdq6TVrTU/0Aad3oC62/M984fzY2xVTwKBUFK6aw
0Xf9Uc10h+eGc0xAm2zRMNuxPCIAm6W4CPBxDsuBjbsEY/wPXYGlW4E1XYoRT9zB
cK0ABucni+Uj3cZEMGFE+6wlHO+IN8vmB+VkccQp/IX/c1Zzsl1Cvkj8umtIXs+0
EjIs6XqQQ8KmYnhzKSPuFwGYdOAF3TpTQ/QKc3I64YaGfzQHHduk+0GKTFa5MGBj
UD+Sm3sgHBX37KGCsftscAZhv/adbq1j6vR7cBp9eT3g5PGnUWI83dKNzAR0g6Y3
PJWYX3pDsVdGGQ53jUxb/5828ReOXWwQNajCwaIaXyiN+kwj6Ct9o74jWOMCoJ6H
8rAjZAzzbkAY4jBFwQs+VyExI9c6JbVBmah+3Dbdqz4Q8WiyvnIIz4xanUrBdjPS
bWUzdxLBC84Djz6M9Y3vwBNXeVd3q1BlZ0DS9ztoHFA/FCBxz0IFXzdi7Fsu/R5c
r7XU8csWyKY=
=cxw7
-----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 26 Jun 2015 10:15:16 GMT) (full text, mbox, link).
Acknowledgement sent
to Mattia Rizzolo <mattia@mapreri.org>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 26 Jun 2015 10:15:16 GMT) (full text, mbox, link).
control: reopen -1
control: found -1 1.4.0-4
On Wed, Jun 24, 2015 at 10:31:35PM +0000, Mattia Rizzolo wrote:
> On Thu, Jun 25, 2015 at 12:01:06AM +0200, Yann Dirson wrote:
> > On Fri, Jun 19, 2015 at 11:03:21PM +0000, Mattia Rizzolo wrote:
> > > On Fri, Jun 19, 2015 at 7:16 PM, Yann Dirson <ydirson@free.fr> wrote:
> > > > Can you look at the process tree under the test run, and possibly get
> > > > a look at what the leaf processes are doing ?
> > >
> > > can you tell me more precisely what i should do? run the build and?
> >
> > When it gets stuck, I'd use something like "pstree -p $(pidof
> > debuild)" to get an idea of what's still running. If it's a test, "ps
> > l" should tell us which one it is, and with some luck we'll be able to
> > see the problem by just looking at that particular test. If that's
> > not sufficient, I'd go with "strace -p" first.
>
> just manually ran a build on the host the very same way the job does and it
> went good. Dunno maybe this is trigger also by a particulr load, and a load of
> ~60 is not enough (and it's too much, who knows..).
> FTR it took 6:16 minutes.
hanged again.
https://jenkins.debian.net/view/reproducible/job/reproducible_builder_theta/17648/consoleFull
This will run for 12 houts before getting killed by the timeout (or before by
us, if the process will gets too eager).
dh_auto_test,30415 -w /usr/bin/dh_auto_test --max-parallel=1
└─make,31723 -j1 check
└─bash,31841 -c...
└─bash,36187 -c...
└─make,36191 check
└─bash,3862 -ec cd large && for i in *.sh ; \\\012do \\\012\011echo Running test `pwd`/$i; \\\012\011/bin/bash $i || exit 1; \\\012done
└─bash,3864 admin.sh
└─bash,3882 admin.sh
└─yes,3884 %C%
that's.. umh..
strace -p 3884 (e.g. the yes process) flooded my terminal with
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
write(1, "%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n%C%\n"..., 4096) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=3884, si_uid=1111} ---
As I haven't killed it i can still run stuff if you point me at something.
sad, but thanks for your support :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Bug reopened
Request was from Mattia Rizzolo <mattia@mapreri.org>
to 788863-submit@bugs.debian.org.
(Fri, 26 Jun 2015 10:15:16 GMT) (full text, mbox, link).
No longer marked as fixed in versions cssc/1.4.0-4.
Request was from Mattia Rizzolo <mattia@mapreri.org>
to 788863-submit@bugs.debian.org.
(Fri, 26 Jun 2015 10:15:17 GMT) (full text, mbox, link).
Marked as found in versions cssc/1.4.0-4.
Request was from Mattia Rizzolo <mattia@mapreri.org>
to 788863-submit@bugs.debian.org.
(Fri, 26 Jun 2015 10:15:18 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 26 Jun 2015 21:30:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Yann Dirson <ydirson@free.fr>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 26 Jun 2015 21:30:09 GMT) (full text, mbox, link).
To: Mattia Rizzolo <mattia@mapreri.org>, 788863@bugs.debian.org
Subject: Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the tests
Date: Fri, 26 Jun 2015 23:26:17 +0200
On Fri, Jun 26, 2015 at 10:12:58AM +0000, Mattia Rizzolo wrote:
> As I haven't killed it i can still run stuff if you point me at something.
The "yes.c" provided by the testsuite does not handle write errors,
that's easy enough to fix. I guess the author expected that when the
yes|head is over and the script finishes, everyone gets wiped by
SIGHUP, but that in your case the pipe is broken but the script did
not finish.
If it's still time, could you get a look at what those admin.sh
processes are waiting for ?
Damned "portable" test suite :)
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Fri, 26 Jun 2015 23:27:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Mattia Rizzolo <mattia@mapreri.org>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Fri, 26 Jun 2015 23:27:04 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Yann Dirson <dirson@debian.org>: Bug#788863; Package cssc.
(Sat, 27 Jun 2015 07:00:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Yann Dirson <ydirson@free.fr>:
Extra info received and forwarded to list. Copy sent to Yann Dirson <dirson@debian.org>.
(Sat, 27 Jun 2015 07:00:03 GMT) (full text, mbox, link).
To: Mattia Rizzolo <mattia@mapreri.org>, 788863@bugs.debian.org
Subject: Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the tests
Date: Sat, 27 Jun 2015 08:57:16 +0200
On Fri, Jun 26, 2015 at 11:23:33PM +0000, Mattia Rizzolo wrote:
> Interesting enough this did not fail the build, though (i think the
> "exit_group(0)" above has something to do with this).
Thanks much for those details!
The "yes" process is piped into a "head", so its exit code is ignored,
that's normal.
If the whole thing exits when yes does, then 1.4.0-5 will probably not
cause any problem any more.
What I'm wondering, though, is whether the /bin/sh selection has any
influence, maybe this strange behaviour could be a shell bug.
I assume this server uses dash as sh, and in this case it could be
worth checking if using bash for this script instead triggers the same
behaviour. In case you could try rerunning 1.4.0-4 with the following
patch, we could get some more insight in this and possibly expose the
real culprit :)
--- tests/Makefile.am.orig 2015-06-27 08:48:04.598905333 +0200
+++ tests/Makefile.am 2015-06-27 08:48:32.206854551 +0200
@@ -17,7 +17,7 @@
$(SHELL) $$i || exit 1; \
done'
-
+test-admin: SHELL=/bin/bash
test-admin: links
$(SHELL) -ec 'cd admin && for i in *.sh ; \
do \
TIA,
--
Yann
Reply sent
to Mattia Rizzolo <mattia@mapreri.org>:
You have taken responsibility.
(Sat, 27 Jun 2015 14:27:09 GMT) (full text, mbox, link).
Notification sent
to Mattia Rizzolo <mattia@mapreri.org>:
Bug acknowledged by developer.
(Sat, 27 Jun 2015 14:27:09 GMT) (full text, mbox, link).
Version: 1.4.0-5
On Sat, Jun 27, 2015 at 08:57:16AM +0200, Yann Dirson wrote:
> On Fri, Jun 26, 2015 at 11:23:33PM +0000, Mattia Rizzolo wrote:
> > Interesting enough this did not fail the build, though (i think the
> > "exit_group(0)" above has something to do with this).
>
> The "yes" process is piped into a "head", so its exit code is ignored,
> that's normal.
well, there are ways to get the exit code of a piped process, namely the
PIPESTATUS array (bash only) and a set -something i don't currently recall (I
don't even recall if that's bash only too).
> If the whole thing exits when yes does, then 1.4.0-5 will probably not
> cause any problem any more.
good!
> What I'm wondering, though, is whether the /bin/sh selection has any
> influence, maybe this strange behaviour could be a shell bug.
>
> I assume this server uses dash as sh, and in this case it could be
> worth checking if using bash for this script instead triggers the same
> behaviour. In case you could try rerunning 1.4.0-4 with the following
> patch, we could get some more insight in this and possibly expose the
> real culprit :)
yeah, that's a standard sid chroot, so with /bin/sh → /bin/dash, indeed.
> --- tests/Makefile.am.orig 2015-06-27 08:48:04.598905333 +0200
> +++ tests/Makefile.am 2015-06-27 08:48:32.206854551 +0200
> @@ -17,7 +17,7 @@
> $(SHELL) $$i || exit 1; \
> done'
>
> -
> +test-admin: SHELL=/bin/bash
> test-admin: links
> $(SHELL) -ec 'cd admin && for i in *.sh ; \
> do \
sorry, but I don't really feel like yet another iteration of this, also because
the last manual run (directly over the shell) just didn't show this bug.
Though, the 1.4.0-5 one built just fine in 453 seconds and as such I
unblacklisted the package :)
Thanks very much for your help!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.