Bug#822722: RFS: tldp/0.7.7 [ITP #822181]
Greetings Gianfranco,
>as you wish, but...
>http://debomatic-amd64.debian.net/distribution#unstable/tldp/0.7.12-1/buildlog
>
>the three test are failing on a clean sbuild environment
I did not know about 'sbuild'. Now I do.
Is this the tool that is used for building all packages to generate
the distributions?
If so, then I'll stop building with pbuilder and gbp buildpackage.
I installed and started learning 'sbuild'. When I run 'sbuild
--verbose' on my Debian unstable (sid), the build succeeds. See
below the relevant snippet from debomatic and then mine. What am I
doing wrong that mine builds when it shouldn't?
'sbuild --verbose' log from debomatic
=====================================
I: pybuild base:184: cd /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build; python3.5 -m nose tests
.............................................................................................................FF..FException
ignored in: <bound method _TemporaryFileCloser.__del__ of <tempfile._TemporaryFileCloser object at 0x7f96cbd5e400>>
Traceback (most recent call last):
File "/usr/lib/python3.5/tempfile.py", line 589, in __del__
self.close()
File "/usr/lib/python3.5/tempfile.py", line 585, in close
unlink(self.name)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tldp-test-8hjyjzpr/tmppvdatun3'
'sbuild --verbose' log from my node that tracks unstable
========================================================
I: pybuild base:184: cd /<<PKGBUILDDIR>>/.pybuild/pythonX.Y_3.5/build; python3.5 -m nose tests
................................................................................................................................
----------------------------------------------------------------------
Ran 128 tests in 1.478s
OK
I have tried to reproduce (or provoke) the failure and cannot seem
to do so. Any tips on how can I reproduce the environment in which
the test suite is failing?
I have made two minor improvements to the test suite for clarity and
explicitness:
* when mangling the mode, reset the file mode before returning
* be more explicit about the permission or access testing
However, both before and after my changes, the tests still succeed
for me on Python 3.5 (on Debian unstable and OpenSUSE-13.2). I.e. I
cannot reproduce.
How do I discover the environment in which the tests are failing or
should I simply create another release with my minor changes and
upload to mentors.debian.org?
>borgbackup is maintained with mixed histories (debian and upstream git commits)
>in the borg.git debian repository (collab-maint)
OK, I'll look for it. I went to the upstream, I guess. Thank you.
>>I used dput 'dput mentors tldp_0.7.12-1_source.changes' and I got
>>back a bunch of output (ending like this).
>
>
>completely correct!
>
>anyway, it was failing to build on DebOMatic sbuild, but not on local
>pbuilder-dist environment.
>
>I sponsored it to new queue, we will see once the package is
>accepted how the build goes with Ubuntu builders (please don't
>forget that :p)
Got it! I have built and installed on Ubuntu-16.04 (locally) and
that seems to work fine.
>in the meanwhile feel free to experiment some builds and ask me for
>sponsorship of a -2 revision if you have a testsuite fix.
I will do so. I appreciate all of your guidance, help and advice,
Gianfranco.
>thanks for your contribution to Debian!
And, I'm very happy to see that I have crossed the minimum bar.
-Martin
--
Martin A. Brown
http://linux-ip.net/
Reply to: