Re: testing the test environment

[Michael Crusoe <michael.crusoe@gmail.com>]

Dear Maarten,

I know how frustrating it can be!

Does https://ci.debian.net/doc/file.MAINTAINERS.html#label-How+can+I+reproduce+the+test+run+locally-3F help? I use both the pbuilder hook and sbuild with lxc setups.

The pbuilder hook is convenient as it gets run everytime I build a package with pbuilder (I actually use cowbuilder-dist, but it is all the same). However it inherits all the build-depends from the source package, which might be more than is defined in debian/tests/control. So if I'm having a specific autotesk issue I use the sbuild route. Sbuild can also test a modified debian/tests/* without rebuilding a package, which can save a lot of time in some circumstances.

-- 
Michael R. Crusoe

On Sun, Nov 8, 2020, 12:51 Maarten L. Hekkelman <maarten@hekkelman.com> wrote:

Hi,

Is it possible to test (debug) the environment in which packages are built and packaged? Or do I continue by guessing what might cause a problem and try to see if my guess is correct by submitting a new version?

Libzeep e.g. has test code and this fails with a 'host not found' error. This is probably because my test code tries to connect to 127.0.0.1 and I should perhaps have used 'localhost' instead. But I'm not sure if that will work. So now I can create a patch replacing the numeric version with the string and hope this will work. I'd rather be sure this is the fix needed before I submit another version.

regards, -maarten