Python tests fail due to missing extension libraries when building only wt and wiredtiger_python targets

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: Build
    • Security Level: Public (Available to anyone on the web)
    • Storage Engines - Persistence
    • 500.749
    • SE Persistence - 2026-04-24
    • 1

      Issue Summary

      Running Python tests after compiling only the wt and wiredtiger_python targets results in failures due to missing extension libraries (e.g., 'palite' in 'page_log'). The error message is:

      Exception: test_layered85.test_layered85.test_scan_completeness_after_checkpoint_removes_key_mid_scan(palite): page_log/palite: no extensions library found matching 'palite' in 'page_log'
      

      Context

      • Build was performed using:
        cmake -DPYTHON3_REQUIRED_VERSION=3.10 -G Ninja ../. && ninja wt wiredtiger_python
        
      • Attempting to run a Python test (e.g., test_layered85.py) fails because required extension libraries are not built.
      • The expectation was that compiling wt and wiredtiger_python would be sufficient for running Python tests.
      • A full build with ninja resolves the issue, indicating additional targets are required for extensions.

      Proposed Solution

      • Update build documentation or scripts to clarify that running Python tests requires building extension libraries.
      • Consider adding a dedicated build target (e.g., wiredtiger_python_tests) that includes all necessary dependencies for Python test execution.
      • Alternatively, enhance the wiredtiger_python target to depend on extension libraries needed for tests.

      Original Slack thread: Slack Thread
      This ticket was generated by AI from a Slack thread.

            Assignee:
            Etienne Petrel
            Reporter:
            Memento Slack Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: