[Debian-med-packaging] Bug#735883: auto_test failing for python-csb

[Tomas Di Domenico]

Hi Andreas,

Right, I had missed that spot. Before applying the fix, however, I'd
like to replicate the error and make sure it's fixed locally, both to
make sure it'll work, and to learn about the test system in the process.

I've been trying to get the tests to fail in the way it's reported, but
I haven't been able to. By doing some research I ended up with this command:

sudo adt-run --user=<a_normal_user> --no-built-binaries --built-tree=.
--- adt-virt-null

but still the tests run without any problems.

Is there a way to replicate the test exactly as it is run when uploaded?

Thanks!
Tomás


On 21/01/14 09:07, Andreas Tille wrote:
> Hi Tomás,
> 
> On Sat, Jan 18, 2014 at 05:45:31PM +0100, Tomás Di Domenico wrote:
>> Greegins, all.
>>
>> A bug that I had marked as closed has been reopened (or rather,
>> re-reported) [1]. It seems like when running the tests as specified in
>> debian/rules/override_dh_auto_test,the test suite tries to write to a
>> forbidden location. The issue is that upon our request, after having
>> faced the same problem in a previous release, upstream has added a
>> parameter to specify the write directory. I added this parameter to the
>> auto_test command, and it works perfectly when I run git-buildpackage.
>> It also succeeds when running the test command manually (just to
>> confirm, I do get the reported error if I leave out the new parameter).
> 
> The issue is solved for *building* the package.
>  
>> I'm a bit at a loss here. I don't quite understand what could be causing
>> the tests to try and write somewhere else than where the
>> --generated-resources arguments is indicating.
> 
> The bug report (in CC - it always makes sense to keep the reporter and
> readers of the bug report informed) is about autopkgtest which is some
> test suite which runs on all packages that have set
> 
>    XS-Testsuite: autopkgtest
> 
> in d/control.  So I think to fix the bug you need to pass the very same
> option you used in override_dh_auto_test in debian/tests/build as well
> to fix the problem.
> 
> Hope this helps
> 
>       Andreas.
>