I am plannig to upgrade twisted's buildbot in the near future. In
preperation for that, I am going to take down the production buildbot
on Tuesday, June 26, around 1600 UTC.
During that time, the result of any builds done will be lost. Thus, I'd
ask that people avoid committing to trunk during that time.
I will send a reminder before I take down the buildbot both here, and on
#twisted and #twisted-dev.
hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
I'm happy to announce a new project, subunitreporter
<https://pypi.org/project/subunitreporter/>, which provides a reporter
plugin for Trial which emits subunit v2 output.
Twisted includes a subunit v1 reporter for Trial. However, the v1 output
format must generally be converted to the v2 format before much can be done
with it. Additionally, the reporter included with Twisted does not include
timing information. The output generated by subunitreporter does include
One useful thing to do with a subunit v2 stream is convert it to junitxml
and let CircleCI ingest it. This is precisely the reason I've written this
reporter. You can see this in action on some recent Tahoe-LAFS builds. In
all cases, builds now include a summary of the number of tests run.
On success <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/438>, slowest
test are reported.
On failure <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/379>, the
failing tests and their failure details are summarized.
Further analysis and reporting
I find this to be a nice development convenience when using CircleCI.
Other build systems are likely to be able to use either the subunit v2
output or (like CircleCI) the equivalent junitxml which can trivially be
produced from the subunit v2 output.
My thanks to Least Authority TFA GmbH <https://leastauthority.com/> for
sponsoring these specific Tahoe-LAFS infrastructure improvements as well as
the subunitreporter project.
This email is at Glyph's request (see the review). I've made the
requested changes and, aside from a pre-existing twistedchecker bug, all
tests are passing. 7927 is again ready for review.
The PR is here:
Ticket is here:
As with the last review, I will try to incorporate any comments quickly.
This should be helpful to new Twisted users as the default logger will
actually print tracebacks.
I have a minor PR that was reviewed and labeled "cleared to land" a
while back, but three months have passed since then and it's still
unmerged. Is there something else I need to do to move this along, or
did it just fall through the cracks?