homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nnorwitz
Recipients
Date 2004年01月07日.22:06:55
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=33168
run the test with the -v flag: ./python
./Lib/test/regrtest.py -v test_mmap
I think only everything should be fine up to copy-on-write
tests. Here's what a good run looks like:
[neal@epoch c3]$ ./python ./Lib/test/regrtest.py -v test_mmap
test_mmap
<type 'mmap.mmap'>
 Position of foo: 1.0 pages
 Length of file: 2.0 pages
 Contents of byte 0: '\x00'
 Contents of first 3 bytes: '\x00\x00\x00'
 
 
 Modifying file's content...
 Contents of byte 0: '3'
 Contents of first 3 bytes: '3\x00\x00'
 Contents of second page: '\x00foobar\x00'
 Regex match on mmap (page start, length of match): 1.0 6
 Seek to zeroth byte
 Seek to 42nd byte
 Seek to last byte
 Try to seek to negative position...
 Try to seek beyond end of mmap...
 Try to seek to negative position...
 Attempting resize()
 Creating 10 byte test data file.
 Opening mmap with access=ACCESS_READ
 Ensuring that readonly mmap can't be slice assigned.
 Ensuring that readonly mmap can't be item assigned.
 Ensuring that readonly mmap can't be write() to.
 Ensuring that readonly mmap can't be write_byte() to.
 Ensuring that readonly mmap can't be resized.
 Opening mmap with size too big
 Opening mmap with access=ACCESS_WRITE
 Modifying write-through memory map.
 Opening mmap with access=ACCESS_COPY
 Modifying copy-on-write memory map.
 Ensuring copy-on-write maps cannot be resized.
 Ensuring invalid access parameter raises exception.
 Test passed
1 test OK.
History
Date User Action Args
2007年08月23日 14:10:37adminlinkissue678250 messages
2007年08月23日 14:10:37admincreate

AltStyle によって変換されたページ (->オリジナル) /