Message286002
It has been observed that posix_fadvise will not report the original error if the syscall fails. Eg. https://bugs.alpinelinux.org/issues/6592
>>> os.posix_fadvise(-1, 0, 0, os.POSIX_FADV_DONTNEED)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 0] Error
Should report EBADF
>>> os.posix_fadvise(16, 0, 0, os.POSIX_FADV_DONTNEED)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 0] Error
Ditto
>>> os.posix_fadvise(0, 0, 0, 12345)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 0] Error
Should be EINVAL
...
This might be because unlike most syscall wrappers posix_fadvise does not set errno but only returns it. |
|
Date |
User |
Action |
Args |
2017-01-22 11:20:17 | enkore | set | recipients:
+ enkore |
2017-01-22 11:20:17 | enkore | set | messageid: <1485084017.58.0.131551905677.issue29342@psf.upfronthosting.co.za> |
2017-01-22 11:20:17 | enkore | link | issue29342 messages |
2017-01-22 11:20:17 | enkore | create | |
|