Feat/even more faster testing

[tetelio]

Summary

Goal is having faster and reliable CI for dlt OSS.

What was done?

• Common tests split into parallel jobs — Instead of one long job per OS/Python version, common CI now runs three suites in parallel: core/min-deps/workspace, full pipeline, and SQLAlchemy 2. Same coverage, shorter wall-clock time.
• Source tests split — Local source jobs separate “sources load” (SQLAlchemy 1.4) from sql_database (SQLAlchemy 2) so they run concurrently instead of back-to-back.
• dbt runner split — No-venv and venv dbt tests run as parallel matrix jobs.
• Lighter Lance S3 CI — Non-essential Lance S3 tests no longer run on every PR (essential coverage unchanged). A remote destination, especially if slow, can only be executing all essential and non essential tests only for a limited amount of time. Does it really still need to execute all tests every CI run?
• Docs CI runners — Docs snippet tests use faster Blacksmith runners.
• Clearer job names — Shorter, consistent names in the GitHub checks UI (lint, common, local, remote, etc.).
• Automatic retries — Integration-heavy suites (local load, remote destinations, dashboard e2e) retry once on failure to absorb transient flakes.
• Local common scope — Workspace tests removed from make test-common (still covered in CI); keeps the default local pre-push loop focused and faster.
• Fixed flaky duckdb local desitnation test with incosistent dataset dimension
• TODO: @burnash @rudolfix we need to remove the essential mark from remote destination tests that dont need to be run every CI run (especially if they take very long).

IMPORTANT and related to (#3997)

• Optional early destination runs — PR label test-destinations-early starts local/remote destination, local source, and dbt jobs without waiting for common to finish (lint and common still run in order). Use only when you have already run lint and common locally. The related PR offers running a set of prek pre-push convenience commands to make sure make fl and make test-common-p are run locally before any push, in order to avoid wasting remote destination CI time, the slowest.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	docs	101dfdd	Commit Preview URL Branch Preview URL	May 29 2026, 10:48 AM