Repository navigation
Windows Data tests are near the 20-minute CI timeout #2770
Description
On windows-latest, FluentCMS.Data.Tests is close to the job's 20-minute timeout. One run on the #2765 branch, after main was merged into it, was cancelled at 20 minutes in the Test step (run 41775547580).
Durations of Data.Tests.dll on Windows:
| Run | Commit | Data tests |
|---|---|---|
| 41771026856 | #2766 branch (before #2767) | 9m 07s |
| 41745568643 | #2764 branch | 10m 35s |
| 41773041495 | #2767 branch | 10m 35s |
| 41770801084 | #2765 branch (before #2767) | 11m 16s |
| 41774459467 | main after #2767 |
14m 58s |
| 41775547580 | #2765 with main merged |
over 17m, timed out |
The jump after #2767 may be noise. It may also come from the extra BEGIN IMMEDIATE/COMMIT per write that #2767 adds, or from IMMEDIATE writers now waiting on readers where they used to fail fast. The Ubuntu runs don't show it.
What needs doing:
- Time the Data tests on Windows with and without the Run SQLite writes in a transaction so they wait for readers #2767 interceptors, and find where the time goes. The slowest tests or classes are a good place to start, for example SQLite file databases, contention tests, and job runner tests that wait on timeouts.
- Bring the Windows Data tests well under the timeout again. Fix the cause if Run SQLite writes in a transaction so they wait for readers #2767 is the reason; raising
timeout-minutesalone is not the fix.
Activity