Message374725
Two tests in test_pathlib test that the files created have mode o666 (rw-rw-rw).
However, on a filesystem (in my case NFS) configured to never permit global write - the test will always fail.
Is this something to be concerned about?
I can think of a few possible ways to react to an exception such as this, e.g., rather than 'FAIL' outright, try umask(2).
++++++++
======================================================================
FAIL: test_open_mode (test.test_pathlib.PosixPathTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/data/prj/python/src/py38-3.8.5/Lib/test/test_pathlib.py", line 2210, in test_open_mode
self.assertEqual(stat.S_IMODE(st.st_mode), 0o666)
AssertionError: 436 != 438
======================================================================
FAIL: test_touch_mode (test.test_pathlib.PosixPathTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/data/prj/python/src/py38-3.8.5/Lib/test/test_pathlib.py", line 2223, in test_touch_mode
self.assertEqual(stat.S_IMODE(st.st_mode), 0o666)
AssertionError: 436 != 438
----------------------------------------------------------------------
++++++++
Just to verify it does work when on a 'local' filesystem.
cp -rp build /tmp/build
mv build build.nfs
ln -s /tmp/build build
== Tests result: SUCCESS ==
1 test OK.
Total duration: 7.8 sec
Tests result: SUCCESS |
|
Date |
User |
Action |
Args |
2020-08-03 07:06:46 | Michael.Felt | set | recipients:
+ Michael.Felt |
2020-08-03 07:06:46 | Michael.Felt | set | messageid: <1596438406.32.0.128608739111.issue41461@roundup.psfhosted.org> |
2020-08-03 07:06:46 | Michael.Felt | link | issue41461 messages |
2020-08-03 07:06:45 | Michael.Felt | create | |
|