[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Eryk Sun added the comment: > Given that this requirement is not universal and because a leading > slash controls other behaviors on platforms like Windows Forward slash has no special meaning anywhere in the names of NT objects, such as memory Section objects (aka file-mapping objects) and

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: FYI the test also failed on AMD64 FreeBSD 10-STABLE Non-Debug 3.x: https://buildbot.python.org/all/#/builders/167/builds/600 I will keep on eye on this buildbot worker as well ;-) -- ___ Python tracker

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Davin Potts added the comment: Closing. Thank you Giampaolo for jumping in so quickly to review! Thank you Victor for catching this on the buildbot. Though what is this talk of "_if_ the color changes"? ;) -- resolution: -> fixed stage: patch review -> resolved status: open ->

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Davin Potts added the comment: New changeset aadef2b41600cb6a4f845cdc4cea001c916d8745 by Davin Potts in branch 'master': bpo-36102: Prepend slash to all POSIX shared memory block names (#12036) https://github.com/python/cpython/commit/aadef2b41600cb6a4f845cdc4cea001c916d8745 --

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Change by Rohit travels and tours : -- type: -> resource usage ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

STINNER Victor added the comment: Apply the patch, we will see if the buildbot color changes :-) -- ___ Python tracker ___ ___

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Change by Davin Potts : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Davin Potts added the comment: I have locally tested GH-12036 on all 5 of the aforementioned OSes and all are made happy by the patch. Victor: If we want to go ahead and apply this patch right away to hopefully make the FreeBSD buildbot go green, the nature of this change is sufficiently

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Change by Davin Potts : -- keywords: +patch pull_requests: +12065 stage: -> patch review ___ Python tracker ___ ___

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Davin Potts added the comment: In local testing, I found the following systems to impose the leading slash as a requirement for simply creating a shared memory block: * NetBSD 8.0 * FreeBSD 12.x * TrueOS 18.12 (the OS formerly known as PC-BSD) I found the following systems to have no

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

Davin Potts added the comment: Though apparently undocumented on FreeBSD, their implementation of shm_open differs from others in the following way: all names for shared memory blocks *must* begin with a slash. This requirement does not exist on OpenBSD. According to its man page on

[issue36102] TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x

New submission from STINNER Victor : TestSharedMemory fails on AMD64 FreeBSD CURRENT Shared 3.x: * The tests should be skipped on this buildbot worker * Or the feature should be fixed on FreeBSD https://buildbot.python.org/all/#/builders/168/builds/617 Example: ERROR: