Skip to content

Test: Always run the TypedPython leak test now that #98 is fixed - #119

Merged
b-re-w merged 1 commit into
developfrom
feat/tp-leak-test
Oct 3, 2026
Merged

b-re-w merged 1 commit into
developfrom
feat/tp-leak-test

Conversation

@b-re-w

@b-re-w b-re-w commented Oct 3, 2026

Copy link
Copy Markdown
Member

Follow-up to #98 (merged via #118) and #45.

  • TypedPythonKotlinCallTest.tenThousandCompiledCallsLeakNoReferenceAndNoKotlinHandle no longer skips on -Dtypedpython.leakTest. That property never reached the test JVM from the Gradle CLI anyway.
  • TypedPythonBridge.kt: corrected the comment that blamed close() inside an upcall for a double release. The crash came from a test wrapping fake addresses as owned objects.

Verification (local, macOS arm64, JDK 21): :ksp-fixtures:app:desktopTest --rerun -PtypedpythonPython=<venv with pyrefly 1.3.2>, test-results deleted first: 79 tests, 0 failures, 0 errors, 0 skipped. The leak test ran (1.29 s) and passed.

Note: without a host Python that has pyrefly (-PtypedpythonPython or python-multiplatform-ksp/.venv), buildTypedPythonBridge is skipped and all four TypedPython tests report skipped. A plain run gave 79/0/0 with 4 skipped for that reason, not because of #98.

@b-re-w
b-re-w merged commit a6dbd7f into develop Oct 3, 2026
5 checks passed
@b-re-w
b-re-w deleted the feat/tp-leak-test branch October 3, 2026 11:04
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.

1 participant