In rekeywording dev-python/jupyter_server-2.3.0 ~riscv, tests case failed in test_atomic_writing_umask: handle_umask = None, tmp_path = PosixPath('/var/tmp/portage/dev-python/jupyter_server-2.3.0/temp/pytest-of-portage/pytest-0/test_atomic_writing_umask0') @pytest.mark.skipif(sys.platform.startswith(win), reason=Windows) def test_atomic_writing_umask(handle_umask, tmp_path): os.umask(0o022) f1 = str(tmp_path / 1) with atomic_writing(f1) as f: f.write(1) mode = stat.S_IMODE(os.stat(f1).st_mode) > assert mode == 0o644 E assert 438 == 420 f = <_io.TextIOWrapper name='/var/tmp/portage/dev-python/jupyter_server-2.3.0/temp/pytest-of-portage/pytest-0/test_atomic_writing_umask0/1' mode='w' encoding='utf-8'> f1 = '/var/tmp/portage/dev-python/jupyter_server-2.3.0/temp/pytest-of-portage/pytest-0/test_atomic_writing_umask0/1' handle_umask = None mode = 438 tmp_path = PosixPath('/var/tmp/portage/dev-python/jupyter_server-2.3.0/temp/pytest-of-portage/pytest-0/test_atomic_writing_umask0') tests/services/contents/test_fileio.py:86: AssertionError
Created attachment 856646 [details] info.txt emerge --info
Created attachment 856648 [details] build-python3_10.log
Just for recording, 438 is 0o666.
This bug only occurs in qemu-user, and all test cases passed on Umatched Board, so not block bug #899984 anymore.
I notice that the previous test was jupyter_server-2.3.0 :P I re-tested 2.4.0 in qemu-user, still failed tests/services/contents/test_fileio.py::test_atomic_writing_umask test case.
This bug is only related to my qemu-user + bwrap test environment. Since the test can pass on the Unmatched Board, I think this bug does not need to be further resolved. Sorry for polluting the list!