Skip to content

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

Closed
Closed
test_mmap: test_access_parameter() failed on ARM64 macOS 3.x with macOS 14 Sonoma#109916
Labels
testsTests in the Lib/test dir

Description

@vstinner
vstinner
opened on Sep 26, 2023

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

Activity

  1. vstinner
    added
    testsTests in the Lib/test dir
    on Sep 26, 2023

  2. ned-deily commented on Sep 26, 2023

    @ned-deily
    ned-deily
    on Sep 26, 2023
    Member

    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.

  3. ned-deily
    closed this as completedon Sep 26, 2023
  4. 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[/+] on Sep 26, 2023

  5. smontanaro commented on Sep 27, 2023

    @smontanaro
    smontanaro
    on Sep 27, 2023
    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.

  6. ned-deily commented on Sep 28, 2023

    @ned-deily
    ned-deily
    on Sep 28, 2023
    Member

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    testsTests in the Lib/test dir

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions