Giorgi / DuckDB.NET / 38820682712

93%

push

github

Skip the connection stress tests when no connection code changed

MultiThreadedStress took 272 of the about 300 s that the tests took on
Windows: 20 tasks open a connection to one of 20 file databases,
insert a row and close it, 1,000 times each. Every other test class
was done after 86 s. On Ubuntu it took 72 s.

It and ConnectionSpeed, which does the same with fewer tasks, have the
trait Stress=Connection now. A step before the tests compares with the
previous push or with the base of the pull request, and leaves them out
unless the change touches the code that opens, shares or closes the
native database: the connection folder, DuckDBConnection, the reader,
the command, prepared statements, the wrapper objects of the bindings,
the DuckDB version, the connection tests or the workflow itself. They
always run for main and tags, scheduled and manual runs, and when there
is no earlier commit to compare with.

On a throwaway branch: a change to ConnectionManager and a change to the
workflow ran them, a change to another test file did not, and that run's
Windows tests took 80 s instead of about 300.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TXdqHuNtM7YXS8B65qdfxX

2052 of 2285 branches covered (89.8%)

Branch coverage included in aggregate %.

3776 of 4012 relevant lines covered (94.12%)

1004155.35 hits per line