Sean Whitton writes ("Bug#1110474: dgit: Some sbuild tests fail under
tests/run-all"):
> The quilt-gbp-build-modes-sbuild and sbuild-gitish tests fail for me
> when run under tests/run-all. Hacking that script such that jcpus=-j1
> avoids the issue.
You don't give an actual error message. (run-all leaves them in files
called .log) Is it stochastic somehow?
> I am not sure that the problem is that my sbuild setup actually can't do
> the parallelism. This problam has only recently emerged, possibly with
> the upgrade to trixie -- but I did make *some* changes to my sbuild
> setup relatively recently.
...
> This text about the unshare backend is suppressed if you have the
> suggested $chroot_mode="schroot" and $schroot="schroot" in your
> ~/.config/sbuild/config.pl -- which I do.
The tests all set HOME, so that they are uninfluenced by (for example)
unwanted things in the user's devscripts or git configuration,
etc. etc.
I have sbuild 0.89.3 and it WFM. All my schroot configuration is in
/etc.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
