Run tests with valgrind locally and in ci

[lovasoa]

Add a CI job to run unit tests under Valgrind to detect memory safety issues.

---

 

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[lovasoa]

@cursoragent valgrind must run in the existing tests (the ones defined with a strategy matrix), not in a new different test.

And do not touch my cargo lock

[cursor]

Perfect! I've successfully updated the PR to address your feedback:

Changes Made

✅ Integrated valgrind into the existing test matrix - Valgrind now runs within the existing test job that uses the strategy matrix (postgres, mysql, mssql, odbc)

✅ Did not touch Cargo.lock - The commit only modifies .github/workflows/ci.yml

How it works:

• Added a valgrind installation step before the tests
• Set CARGO_TARGET_X86_64_UNKNOWN_LINUX_GNU_RUNNER environment variable to run all tests under valgrind
• All four database configurations (postgres, mysql, mssql, odbc) will now run their tests under valgrind
• Valgrind is configured with --error-exitcode=1 to fail CI on memory errors and --leak-check=no to focus on safety errors

The tests have been verified locally and show 0 memory errors from valgrind.

---

 

_{Learn more about Cursor Agents}