Opened at 2011-11-03T20:56:55Z
Last modified at 2021-03-30T18:40:19Z
#1578 new defect
test suite fails on Windows if run from directory with a long name
Reported by: | dloss | Owned by: | daira |
---|---|---|---|
Priority: | normal | Milestone: | soon |
Component: | code | Version: | 1.9.0b1 |
Keywords: | windows test docs | Cc: | |
Launchpad Bug: |
Description (last modified by daira)
When the Tahoe-LAFS test suite (python setup.py test) is run on Windows from directory with a very long path name, several tests fail:
FAILED (skips=16, expectedFailures=3, failures=1, errors=76, successes=971)
Attachments (1)
Change History (13)
Changed at 2011-11-03T20:57:30Z by dloss
comment:1 Changed at 2011-11-03T20:58:13Z by dloss
Maximum path length on Windows is 255 UTF-16 characters: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath
comment:2 Changed at 2011-11-03T20:58:57Z by dloss
If the path is short enough, spaces in the path name do _not_ cause errors.
comment:3 follow-up: ↓ 4 Changed at 2011-11-19T02:18:14Z by davidsarah
- Component changed from unknown to code
- Keywords windows docs added
- Owner changed from nobody to somebody
It isn't clear that this is fixable with reasonable effort. Although the Win32 API does allow paths up to approximately 32767 UTF-16 code units if prefixed by \\?\, supporting that might require changes in Python, or else careful avoidance (also in Twisted trial) of certain Python APIs.
Perhaps we should have the test suite warn at the start if it is run from a directory with a long path.
comment:4 in reply to: ↑ 3 Changed at 2011-11-19T02:41:33Z by zooko
Replying to davidsarah:
It isn't clear that this is fixable with reasonable effort. Although the Win32 API does allow paths up to approximately 32767 UTF-16 code units if prefixed by \\?\, supporting that might require changes in Python, or else careful avoidance (also in Twisted trial) of certain Python APIs.
Perhaps we should have the test suite warn at the start if it is run from a directory with a long path.
The latter sounds fine to me.
comment:5 Changed at 2012-03-29T23:08:53Z by davidsarah
- Keywords test added
- Owner changed from somebody to davidsarah
- Status changed from new to assigned
- Summary changed from Test suite fails on Win32 if run from directory with a long name. to Test suite fails on Windows if run from directory with a long name.
comment:6 Changed at 2012-03-29T23:09:20Z by davidsarah
- Milestone changed from undecided to eventually
- Summary changed from Test suite fails on Windows if run from directory with a long name. to test suite fails on Windows if run from directory with a long name
comment:7 Changed at 2012-04-01T04:32:05Z by davidsarah
- Priority changed from minor to normal
comment:8 Changed at 2014-10-11T23:15:56Z by daira
- Description modified (diff)
- Milestone changed from eventually to 1.12.0
- Owner changed from davidsarah to daira
- Status changed from assigned to new
comment:9 Changed at 2016-03-22T05:02:25Z by warner
- Milestone changed from 1.12.0 to 1.13.0
Milestone renamed
comment:10 Changed at 2016-06-28T18:17:14Z by warner
- Milestone changed from 1.13.0 to 1.14.0
renaming milestone
comment:11 Changed at 2020-06-30T14:45:13Z by exarkun
- Milestone changed from 1.14.0 to 1.15.0
Moving open issues out of closed milestones.
comment:12 Changed at 2021-03-30T18:40:19Z by meejah
- Milestone changed from 1.15.0 to soon
Ticket retargeted after milestone closed
error messages