➜

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 yan12125
Recipients aeros, asvetlov, benjamin.peterson, nanjekyejoannah, njs, vstinner, yan12125, yselivanov
Date 2019-11-08.10:12:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573207956.08.0.747650911304.issue38692@roundup.psfhosted.org>
In-reply-to
Content 
I got a failure in newly added test_pidfd_open:

======================================================================
FAIL: test_pidfd_open (test.test_posix.PosixTester)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/python-git/src/cpython/Lib/test/test_posix.py", line 1479, in test_pidfd_open
    self.assertEqual(cm.exception.errno, errno.EINVAL)
AssertionError: 1 != 22

----------------------------------------------------------------------

I'm running kernel 5.3.7-x86_64-linode130 with Arch Linux. At first I suspect that it's related to system call filters from systemd as tests are run in a systemd-nspawn container. However, there are still failures after patching systemd with https://github.com/systemd/systemd/commit/9e486265716963439fb0fd7f2a97abf109f24f75.

How about also skipping the test if pidfd_open returns EPERM?
History
Date User Action Args
2019-11-08 10:12:36yan12125setrecipients: + yan12125, vstinner, benjamin.peterson, njs, asvetlov, yselivanov, nanjekyejoannah, aeros
2019-11-08 10:12:36yan12125setmessageid: <1573207956.08.0.747650911304.issue38692@roundup.psfhosted.org>
2019-11-08 10:12:36yan12125linkissue38692 messages
2019-11-08 10:12:35yan12125create