Opened at 2011-05-08T01:00:57Z
Last modified at 2020-01-16T20:29:33Z
#1397 closed defect
CI step to run foolscap test suite — at Version 2
Reported by: | davidsarah | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | soon (release n/a) |
Component: | dev-infrastructure | Version: | 1.8.2 |
Keywords: | buildbot foolscap test | Cc: | |
Launchpad Bug: |
Description (last modified by exarkun)
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
Change History (2)
comment:1 Changed at 2011-05-21T16:30:19Z by davidsarah
- Keywords test added
comment:2 Changed at 2019-07-25T12:58:48Z by exarkun
- Description modified (diff)
- Summary changed from buildbot step to run foolscap test suite to CI step to run foolscap test suite
Note: See
TracTickets for help on using
tickets.
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.