[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2366: set up buildslave to find deprecation warnings

[Tahoe-LAFS]

#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
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+------------------------

Comment (by warner):

 Well, I think it will produce a lot of noise, which is why I'm inclined to
 stick it on a dedicated buildbot column and have some scripts to analyze
 the results. My quick pass shows about 200 lines of `DeprecationWarning`s,
 most of which are twisted's fault (twisted.spread.jelly imports "sets",
 nevow.appserver uses `http.Request.received_headers`, there's a
 `IStreamClientEndpointStringParser` which may or may not be something we
 can fix). I'd like the tooling to have a file with "known and unlikely to
 be fixed" problems, and have it emit errors for anything else. To do that
 on travis.. I guess that'd mean running the tests a second time, with
 warnings turned on, writing the results to a tempfile, running a script
 over the tempfile, and exiting with non-zero if the script identified a
 problem. (as you pointed out, turning on warnings also causes some tests
 to fail because they're expecting silent output of a child process, which
 we'd need to find a way to deal with).

 So I guess no :)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2366#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage