[pkg-bacula-devel] autopkgtest: A choice to be made

Sven Hartge sven at svenhartge.de
Sun Nov 25 22:03:33 GMT 2018

On 25.11.18 22:49, Carsten Leonhardt wrote:
> Sven Hartge <sven at svenhartge.de> writes:

>> I found an even better solution, using BASH_XTRACEFD to redirect the
>> xtrace output to STDOUT. But it only works on "set -x" and not "set -v".
>> Plus: This will properly expand all variables.
>> Con: The output is a bit more noisy.
>> But I think the benefits outweigh the negatives here.
> I agree. I expect that once the autopkgtests are in place, we'll usually
> only look closely at the logs when there are problems, so a bit tendency
> to noisiness sounds like the correct choice.

I agree, on the same reason Policy mandates to make the build as verbose
as possible.

BTW: Do you know who runs the build log scanner? I'd really be
interested why it still has problems with the logs and what lines it
doesn't like, but I can't seem to find that information anywhere on the
QA pages, just the fact that it thinks it found errors, all the while
the manual run from the blhc package shows no errors anymore.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20181125/83374524/attachment.sig>

More information about the pkg-bacula-devel mailing list