ci: fix flaky Postgres test-process segfault at exit

[pratyush618]

Problem

The Rust Tests (PostgreSQL) job intermittently fails: all 98 lib tests pass, then the test binary crashes on exit with signal: 11, SIGSEGV (cargo → exit 101). The SQLite and Redis jobs — same LD_LIBRARY_PATH — never crash; only Postgres does.

Cause

The step ran cargo test --workspace --features postgres,workflows with LD_LIBRARY_PATH="$pythonLocation/lib" (so taskito-python's test binary finds libpython). That directory also ships Python's libssl/libcrypto, which get loaded alongside the OpenSSL that libpq links. Two OpenSSL copies in one process → their atexit cleanup handlers race at process teardown → SIGSEGV after the tests have all passed. It's load/teardown-order dependent, hence flaky, and only the Postgres-linked binary pulls in libpq.

Fix

--exclude taskito-python (the only crate that needs libpython at runtime) and drop LD_LIBRARY_PATH. With Python out of the run, Python's OpenSSL is never loaded, so libpq's is the only copy and there's nothing to race at exit.

No coverage lost: the Postgres storage contract lives in taskito-core and taskito-workflows (both still run here); taskito-python's Rust tests already run in the SQLite job (cargo test --workspace).

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 027f895e-c314-4e57-88d1-a5432b3ddf46

📥 Commits

Reviewing files that changed from the base of the PR and between 2061deb and b2bf7a6.

📒 Files selected for processing (1)

• .github/workflows/ci-rust.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-postgres-openssl-teardown

---

_{Comment @coderabbitai help to get the list of available commands.}