test suite fails on Windows if run from directory with a long name #1578

New Issue

tahoe-lafs · 2011-11-03T20:56:55Z

dloss commented

2011-11-03 20:56:55 +00:00

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)

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)

tahoe-lafs added the

labels 2011-11-03 20:56:55 +00:00

tahoe-lafs added this to the undecided milestone 2011-11-03 20:56:55 +00:00

dloss commented

2011-11-03 20:57:30 +00:00

Attachment tahoe_testwin32_longpaths_error.txt (211910 bytes) added

error messages

**Attachment** tahoe_testwin32_longpaths_error.txt (211910 bytes) added error messages

tahoe_testwin32_longpaths_error.txt

207 KiB

dloss commented

2011-11-03 20:58:13 +00:00

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

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>

dloss commented

2011-11-03 20:58:57 +00:00

If the path is short enough, spaces in the path name do not cause errors.

If the path is short enough, spaces in the path name do _not_ cause errors.

davidsarah commented

2011-11-19 02:18:14 +00:00

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.

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.

tahoe-lafs added

code

and removed

unknown

labels 2011-11-19 02:18:14 +00:00

zooko commented

2011-11-19 02:41:33 +00:00

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.

Replying to [davidsarah](/tahoe-lafs/trac-2024-07-25/issues/1578#issuecomment-86231): > 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.

tahoe-lafs changed title 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.

2012-03-29 23:08:53 +00:00

tahoe-lafs modified the milestone from undecided to eventually

2012-03-29 23:09:20 +00:00

tahoe-lafs changed title 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

2012-03-29 23:09:20 +00:00

tahoe-lafs added

normal

and removed

minor

labels 2012-04-01 04:32:05 +00:00

tahoe-lafs modified the milestone from eventually to 1.12.0

2014-10-11 23:15:56 +00:00

warner commented

2016-03-22 05:02:25 +00:00

Milestone renamed

warner modified the milestone from 1.12.0 to 1.13.0