ci: run the integration suite with the extension's no_error_skip config

Given no --test-config, DuckDB's sqllogictest runner turns any error whose
text contains "HTTP" or "Unable to connect" into a SKIP and exits 0. Over
the http transport every worker error carries "HTTP", so the http lane
could report a real failure as a skip. The extension (vgi main f5aa489)
ships test/configs/no_error_skip.json and wires its own scripts to it;
vgi-python's two direct unittest callers did not:

- ci/run-integration.sh (every CI lane, both invocations) now passes
  --test-config "$VGI_SRC/test/configs/no_error_skip.json" and fails
  fast if the pinned vgi ref lacks it.
- scripts/run_all_tests.sh passes it for the local integration job.
- CLAUDE.md's direct-invocation examples pass it, with a note why.

Run on aarch64 with haybarn-unittest against vgi main f5aa489, the three
CI lanes each show the same 3 failures, all version skew between the
vgi main test tree and the community-published extension CI installs, not
masked errors and not worker bugs: attach_ticket/unsupported.test
(vgi_export_session missing), reflection/vgi_protocols.test (vgi_protocols
missing), table/logging_generator.test (attach_opaque_data_sha256 log
field, vgi ac09b3a). Everything else passes: launch/shm 353/356, http
349/352.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: rustyconover

CLAUDE.md

@@ -96,9 +96,13 @@ e.g. to pass an unusual filter to `unittest`):
 ```bash
 cd ~/Development/vgi
 VGI_TEST_WORKER="uv run --project ~/Development/vgi-python vgi-fixture-worker" \
-    ./build/release/test/unittest "test/sql/integration/*"
+    ./build/release/test/unittest --test-config test/configs/no_error_skip.json "test/sql/integration/*"
 ```
 
+Always pass `--test-config test/configs/no_error_skip.json` to `unittest`: without
+it, DuckDB's runner reports any error mentioning "HTTP" or "Unable to connect" as
+a SKIP and exits 0.
+
 **HTTP transport** (worker as an HTTP server):
 ```bash
 cd ~/Development/vgi
@@ -142,7 +146,7 @@ with elapsed milliseconds. This helps identify slow queries and bottlenecks.
 # Timing output goes to stderr, grep for the bracket-prefixed lines:
 cd ~/Development/vgi
 VGI_TEST_WORKER="uv run --project ~/Development/vgi-python vgi-fixture-worker" \
-    ./build/release/test/unittest "test/sql/integration/table/writable_table*" \
+    ./build/release/test/unittest --test-config test/configs/no_error_skip.json "test/sql/integration/table/writable_table*" \
     2>&1 | grep "^\[stmt\|^\[query" | sort -t']' -k2 -rn
 ```
 
@@ -166,7 +170,7 @@ uv run coverage run -m pytest --no-cov -n auto
 # 3. Run DuckDB subprocess integration tests with coverage
 cd ~/Development/vgi
 VGI_TEST_WORKER="/tmp/vgi-coverage-worker.sh" \
-    ./build/release/test/unittest "test/sql/integration/*"
+    ./build/release/test/unittest --test-config test/configs/no_error_skip.json "test/sql/integration/*"
 
 # 4. Run DuckDB HTTP integration tests with coverage
 cd ~/Development/vgi

ci/run-integration.sh

@@ -336,6 +336,13 @@ EOF
 "$HAYBARN_UNITTEST" "test/_warm.test" >/dev/null 2>&1 || echo "::warning::extension warm step did not fully succeed"
 rm -f "$STAGE/test/_warm.test"
 
+# DuckDB's sqllogictest runner, given no --test-config, turns any error whose
+# text contains "HTTP" or "Unable to connect" into a SKIP and exits 0. Over the
+# http transport every worker error carries "HTTP", so real failures read as
+# skips. The extension ships a config that disables that; every run below uses it.
+TEST_CONFIG="$VGI_SRC/test/configs/no_error_skip.json"
+[ -f "$TEST_CONFIG" ] || { echo "::error::missing $TEST_CONFIG (VGI_REF predates it?)"; exit 1; }
+
 # Run the lane, streaming the native sqllogictest report (a progress line per
 # file + the final "All tests passed (.. N assertions ..)" summary). Out-of-scope
 # tests were dropped at staging; any failed assertion exits non-zero.
@@ -366,7 +373,7 @@ run_unittest() {
   # `set +e` rather than `|| true`: the latter runs before PIPESTATUS is read and
   # overwrites it with true's 0, silently swallowing every real test failure.
   set +e
-  "$HAYBARN_UNITTEST" "$@" 2>&1 | tee "$log"
+  "$HAYBARN_UNITTEST" --test-config "$TEST_CONFIG" "$@" 2>&1 | tee "$log"
   rc="${PIPESTATUS[0]}"
   set -e
   if grep -q 'due to a fatal error condition' "$log"; then

scripts/run_all_tests.sh

@@ -204,11 +204,14 @@ run_integration_job() {
       return 2
       ;;
   esac
+  # --test-config: without it the runner turns any error mentioning "HTTP" or
+  # "Unable to connect" into a SKIP, so a failure can pass as a skip.
   # `~[.]` excludes Catch2-hidden tests, i.e. `*.test_slow` files. The
   # launcher keeps one Python worker warm while unittest advances serially,
   # avoiding both repeated startup and cross-test state contention.
   VGI_TEST_WORKER="$worker" \
-    timeout 600 ./build/release/test/unittest "test/sql/integration/*" "~[.]" >"$INT_LOG" 2>&1
+    timeout 600 ./build/release/test/unittest --test-config test/configs/no_error_skip.json \
+      "test/sql/integration/*" "~[.]" >"$INT_LOG" 2>&1
   local rc=$?
   summarize_integration "$INT_LOG" "$INT_SUMMARY" "$INT_FAILURES"
   echo "exit=$rc" >>"$INT_SUMMARY"