Opened 14 years ago
Last modified 13 years ago
#181 new defect
foolscap.test.test_negotiate.Crossfire[Reverse].test1 fail on Windows
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | unknown | Version: | 0.6.1 |
| Keywords: | windows | Cc: |
Description
[FAIL]
Traceback (most recent call last):
File "C:\cygwin\home\David-Sarah\tahoe\trunk\support\Lib\site-packages\foolscap-0.6.1-py2.7.egg\fo
olscap\test\test_negotiate.py", line 586, in <lambda>
d.addCallbacks(lambda res: self.fail("hey! this is supposed to fail"),
twisted.trial.unittest.FailTest: hey! this is supposed to fail
foolscap.test.test_negotiate.Crossfire.test1
foolscap.test.test_negotiate.CrossfireReverse.test1
but it doesn't fail on Unix, so I think the exception message is misleading.
Change History (2)
comment:1 Changed 13 years ago by
| Milestone: | undecided → 0.6.2 |
|---|
comment:2 Changed 13 years ago by
Note: See
TracTickets for help on using
tickets.
Can we get more information about this? That "hey! this is supposed to fail" message means that it was exercising an error-handling case, and the code under test failed to raise the error it was supposed to. (this predates the clean Deferred-aware
self.shouldFail()utility that I later wrote for Tahoe.. we should probably update the tests to use that construct).