Your message dated Sat, 27 Jun 2015 14:25:58 +0000
with message-id <[email protected]>
and subject line Re: Bug#788863: cssc: FTBFS on jenkins.d.n, hangs during the
tests
has caused the Debian Bug report #788863,
regarding cssc: FTBFS on jenkins.d.n, hangs during the tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
788863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788863
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 `-
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
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 `-
signature.asc
Description: Digital signature
--- End Message ---
