Skip to content

test_mmap: test_access_parameter() failed on ARM64 macOS 3.x with macOS 14 Sonoma #109916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vstinner opened this issue Sep 26, 2023 · 3 comments
Closed
Labels
tests Tests in the Lib/test dir

Comments

@vstinner
Copy link
Member

ARM64 macOS 3.x:

ERROR: test_access_parameter (test.test_mmap.MmapTests.test_access_parameter)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_mmap.py", line 258, in test_access_parameter
    m = mmap.mmap(f.fileno(), mapsize, prot=prot)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PermissionError: [Errno 1] Operation not permitted

build: https://buildbot.python.org/all/#/builders/725/builds/5749

@vstinner vstinner added the tests Tests in the Lib/test dir label Sep 26, 2023
@ned-deily
Copy link
Member

ned-deily commented Sep 26, 2023

Duplicate of #107888. Buildbot was just updated to newly released macOS 14 Sonoma which has this change in OS behavior on Apple Silicon Macs but not Intel Macs.

@ned-deily ned-deily changed the title test_mmap: test_access_parameter() failed on ARM64 macOS 3.x test_mmap: test_access_parameter() failed on ARM64 macOS 3.x with macOS 14 Sonoma Sep 26, 2023
@smontanaro
Copy link
Contributor

I see this was applied to main and the 3.11 branch, but not the 3.12 branch. Is that just a matter of a tight bottleneck in the run-up to the 3.12 release? I think it would be a shame to exclude this fix to a test case.

@ned-deily
Copy link
Member

ned-deily commented Sep 28, 2023

I see this was applied to main and the 3.11 branch, but not the 3.12 branch. Is that just a matter of a tight bottleneck in the run-up to the 3.12 release? I think it would be a shame to exclude this fix to a test case.

There is a 3.12 backport PR pending but has not yet been merged for 3.12.0 final.

@Yhg1s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Tests in the Lib/test dir
Projects
None yet
Development

No branches or pull requests

3 participants