[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2366: set up buildslave to find deprecation warnings
Tahoe-LAFS
trac at tahoe-lafs.org
Wed Jan 21 18:43:54 UTC 2015
#2366: set up buildslave to find deprecation warnings
--------------------------------+----------------------------
Reporter: warner | Owner:
Type: task | Status: new
Priority: normal | Milestone: eventually
Component: dev-infrastructure | Version: 1.10.0
Keywords: | Launchpad Bug:
--------------------------------+----------------------------
#2312 was a `DeprecationWarning` that resulted from Tahoe code misusing an
interface (`twisted.web.Request.setHeader`) and the Twisted folks
eventually reminding people to use it correctly by signalling a warning
unless you did it right. The warning was suppressed on most of our
buildslaves (running py2.7, where `DeprecationWarnings` are not enabled by
default), but a few py2.6 builders noticed it.
It'd be nice to notice these things better. I'd like to set up a builder
that adds {{{PYTHONWARNINGS=default::DeprecationWarning}}}, to re-enable
these warnings (even under python2.7). I'd also like to add some tooling
which gathers the warnings, removes ones that are known problems in other
people's code, and goes red if Tahoe itself triggers anything.
It'd probably be most useful to run this builder with the latest version
of Twisted, maybe even Twisted trunk, to find problems early. Ideally we'd
run this with the full (13-dimensional?) matrix of dependency versions,
but I think Twisted is the one place that's most likely to produce
actionable deprecation warnings.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2366>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list