[Zope3-dev] Win32 Tests - Zope 3 - failures:2

[Tim Peters]

[zope-tests@squishdot.org]
>> ======================================================================
>> Python Version:2.2.3 (#42, May 30 2003, 18:12:08) [MSC 32 bit
>>  (Intel)]
>> Modules included: > Zope3 (HEAD)
>> Running unit tests from D:\ZopeTests\sandbox\Zope3
>> Failure in test test_merge_conflict
>> (zope.fssync.tests.test_fsmerger.TestFSMerger)
>> ...
>> AssertionError: 'l\n' != '<<<<<<<
>> C:\\DOCUME~1\\CHRISW~1\\LOCALS~1\\Temp\\~972-712\\local\\foo\nl\n=
>> ======\nr\n>>>>>>>
>>  C:\\DOCUME~1\\CHRISW~1\\LOCALS~1\\Temp\\~972-713\\remote\\foo\n'  >
>> Failure in test test_merge_diff3
>> (zope.fssync.tests.test_fsmerger.TestFSMerger) ...
>> AssertionError: ['C
>> C:\\DOCUME~1\\CHRISW~1\\LOCALS~1\\Temp\\~972-714\\local\\foo'] !=
>> ['M C:\\DOCUME~1\\CHRISW~1\\LOCALS~1\\Temp\\~972-714\\local\\foo']

[Fred Drake]
> These definately look like a platform-sensitive problem; both of
> these are fine on Linux.

Guido explained this before:  whoever ran these tests on Windows has an
unsuitable diff3.exe on their PATH.  When I run them on Win2K:

"""
test_merge_conflict (zope.fssync.tests.test_fsmerger.TestFSMerger) ...
diff3 doesn't work, diff3 tests disabled
ok
test_merge_diff3 (zope.fssync.tests.test_fsmerger.TestFSMerger) ... ok
"""

Someone for whom these tests fail (they don't fail for me) needs to alter
the diff3_check() method to recognize that their diff3 is unusable, or needs
to fiddle their environment to get their unusable diff3 off their PATH.