Skip to content

Fix SQLite table lock errors in tavern integration tests#1949

Draft
KCarretto wants to merge 1 commit intomainfrom
fix-table-lock-tests-8258895298285432105
Draft

Fix SQLite table lock errors in tavern integration tests#1949
KCarretto wants to merge 1 commit intomainfrom
fix-table-lock-tests-8258895298285432105

Conversation

@KCarretto
Copy link
Collaborator

This change addresses the "table lock" errors causing flaky tests in tavern/internal/http/shell and tavern/internal/portals. The fix involves adding _busy_timeout=10000 to the SQLite connection strings in integration and benchmark tests, allowing the driver to retry when the database is locked. Additionally, tavern/internal/portals/mux/mux_test.go was updated to use unique in-memory database names for each test case, isolating them and preventing contention.


PR created automatically by Jules for task 8258895298285432105 started by @KCarretto

- Added `_busy_timeout=10000` to SQLite DSN in `tavern/internal/http/shell/integration_test.go` and `tavern/internal/portals/integration_test.go` to allow retries on database locks.
- Updated `tavern/internal/portals/mux/mux_test.go` to use unique database names per test (`file:ent_%s`) and added busy timeout, preventing cross-test contention.
- Applied busy timeout to benchmark tests in `tavern/internal/portals/benchmark_test.go` and `tavern/internal/portals/mux/benchmark_test.go`.

These changes resolve flaky test failures caused by "database is locked" errors during concurrent test execution.

Co-authored-by: KCarretto <16250309+KCarretto@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2725    ±0 2725    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1378 2725 2725 0 0 0 0 44.4s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2725 0 0 5.6s

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 5.6s 5.6s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.1s 5.1s
TestInteractiveShell 1 5.1s 5.1s
TestOtherStreamOutput 1 5.0s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.6s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.6s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.6s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

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