Read the Catch2 dialect, so the guard covers a DuckDB consumer - #126

3 test(s) skipped. A skipped test asserts nothing and reports as success. Supply the precondition its guard reads, or remove the guard.

the suite ran 102 tests against a floor of 103. Tests that are not collected are reported nowhere, so a total that falls is how coverage leaves without a skip. Restore them, or lower the floor deliberately in the same commit that removes them.

2 test(s) skipped. A skipped test asserts nothing and reports as success. Supply the precondition its guard reads, or remove the guard.

the suite ran 38 tests against a floor of 39. Tests that are not collected are reported nowhere, so a total that falls is how coverage leaves without a skip. Restore them, or lower the floor deliberately in the same commit that removes them.

the suite ran 3 tests against a floor of 4. Tests that are not collected are reported nowhere, so a total that falls is how coverage leaves without a skip. Restore them, or lower the floor deliberately in the same commit that removes them.

1 test(s) skipped. A skipped test asserts nothing and reports as success. Supply the precondition its guard reads, or remove the guard.

the suite ran 267 tests against a floor of 268. Tests that are not collected are reported nowhere, so a total that falls is how coverage leaves without a skip. Restore them, or lower the floor deliberately in the same commit that removes them.

the suite ran 257 tests against a floor of 268. Tests that are not collected are reported nowhere, so a total that falls is how coverage leaves without a skip. Restore them, or lower the floor deliberately in the same commit that removes them.

11 test(s) skipped. A skipped test asserts nothing and reports as success. Supply the precondition its guard reads, or remove the guard.