[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1397: CI step to run foolscap test suite (was: buildbot step to run foolscap test suite)
Tahoe-LAFS
trac at tahoe-lafs.org
Thu Jul 25 12:58:48 UTC 2019
#1397: CI step to run foolscap test suite
------------------------------------+------------------------------------
Reporter: davidsarah | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: soon (release n/a)
Component: dev-infrastructure | Version: 1.8.2
Resolution: | Keywords: buildbot foolscap test
Launchpad Bug: |
------------------------------------+------------------------------------
Old description:
> Since we haven't been running the foolscap unit tests on a Windows
> platform, several test failures were missed:
> * http://foolscap.lothar.com/trac/ticket/177
> * http://foolscap.lothar.com/trac/ticket/178
> * http://foolscap.lothar.com/trac/ticket/179
>
> If there were a Tahoe buildbot step to run the foolscap test suite, that
> would test the same foolscap that is being used in the Tahoe tests. The
> command line should be
>
> {{{python setup.py trial --reporter=timing --rterror -s foolscap.test}}}
New description:
Since we haven't been running the foolscap unit tests on a Windows
platform, several test failures were missed:
* http://foolscap.lothar.com/trac/ticket/177
* http://foolscap.lothar.com/trac/ticket/178
* http://foolscap.lothar.com/trac/ticket/179
If there were a Tahoe CI step to run the foolscap test suite, that would
test the same foolscap that is being used in the Tahoe tests. The command
line should be
{{{python setup.py trial --reporter=timing --rterror -s foolscap.test}}}
--
Comment (by exarkun):
Buildbot has been decommissioned. I'm not sure that means this suggestion
is obsolete. I'm not going to close this ticket. Instead, I'm modifying
it to make it CIS agnostic.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1397#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list