Opened at 2011-05-08T01:00:57Z
Closed at 2020-01-16T20:29:33Z
#1397 closed defect (somebody else's problem)
CI step to run foolscap test suite
| 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 (4)
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
comment:3 Changed at 2020-01-16T20:27:44Z by exarkun
I suppose Tahoe's Appveyor could be adjusted to run the Foolscap test suite. Foolscap development has slowed significantly so I wonder how valuable this is at this point.
On the other hand, there was just a big development push for Python 3 porting and there may be more similar on the way... However, it would really be preferable if Foolscap just had its own Appveyor CI instead of letting errors make their way all the way to Tahoe-LAFS CI where they disrupt Tahoe-LAFS development.
comment:4 Changed at 2020-01-16T20:29:33Z by exarkun
- Resolution set to somebody else's problem
- Status changed from new to closed
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.