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 enkore
Recipients enkore
Date 2017-01-22.11:20:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485084017.58.0.131551905677.issue29342@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-01-22 11:20:17enkoresetrecipients: + enkore
2017-01-22 11:20:17enkoresetmessageid: <1485084017.58.0.131551905677.issue29342@psf.upfronthosting.co.za>
2017-01-22 11:20:17enkorelinkissue29342 messages
2017-01-22 11:20:17enkorecreate