Skip to content

Conversation

@rwgk
Copy link
Contributor

@rwgk rwgk commented Jan 22, 2024

Description

This is to enable running the test multiple times (e.g. for leak checking), or for compatibility with options such as --runs_per_test.

This PR makes the pybind11 test similar to the corresponding PyCLIF test:

Suggested changelog entry:

This is to enable running the test multiple times (e.g. for leak checking), or for compatibility with options such as `--runs_per_test`.

This PR makes the pybind11 test similar to the corresponding PyCLIF test:

https://github.com/google/clif/blob/e0f4bf60933973b98ddb971750a9929348f84bc2/clif/testing/class_release_gil_before_calling_cpp_dtor.h#L51-L59
@rwgk rwgk marked this pull request as ready for review January 22, 2024 20:02
@rwgk rwgk merged commit 47b666d into google:main Jan 22, 2024
@rwgk rwgk deleted the PopPyGILState_Check_Result branch January 22, 2024 20:02
rwgk added a commit to rwgk/pybind11 that referenced this pull request Feb 15, 2025
…if#30092 (minor fixes).

Note for completeness:

These are identical to the current versions on the pybind11clif main branch (@ commit 4841661df5daf26ecdedaace54e64d0782e63f64):

* test_class_release_gil_before_calling_cpp_dtor.cpp
* test_class_release_gil_before_calling_cpp_dtor.py
rwgk added a commit to pybind/pybind11 that referenced this pull request Feb 16, 2025
)

* Backport of google/pybind11clif#30088 (main PR) and google/pybind11clif#30092 (minor fixes).

Note for completeness:

These are identical to the current versions on the pybind11clif main branch (@ commit 4841661df5daf26ecdedaace54e64d0782e63f64):

* test_class_release_gil_before_calling_cpp_dtor.cpp
* test_class_release_gil_before_calling_cpp_dtor.py

* Fix potential data race in test_class_release_gil_before_calling_cpp_dtor.cpp

The original intent was to let the singleton leak, but making that tread-safe is slightly more involved than this solution. It's totally fine in this case if the RegistryType destructor runs on process teardown.

See also: #5522 (comment)

---------

Co-authored-by: Ralf W. Grosse-Kunstleve <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants