Skip to content

fix: keep set operations after subquery operands at the outer query #1169

fix: keep set operations after subquery operands at the outer query

fix: keep set operations after subquery operands at the outer query #1169

Re-run triggered October 2, 2026 23:17
Status Success
Total duration 16m 10s
Artifacts –

verify.yml

on: pull_request
Classify verification scope
8s
Classify verification scope
Lockfile consistency
22s
Lockfile consistency
Matrix: wheels
Matrix: cache_compile_performance
Matrix: cold_compile_performance
Matrix: compile_performance_ratio
Matrix: dense_compile_performance
Matrix: e2e_shards
Static checks and unit + integration tests
12m 37s
Static checks and unit + integration tests
Formatter performance guards
6m 39s
Formatter performance guards
Performance guards
Performance guards
Rules performance guards
Rules performance guards
PostgreSQL integration and E2E tests
9m 13s
PostgreSQL integration and E2E tests
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Fresh-process compile cache (5000 models)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
DuckDB E2E (CLI commands)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, astral-sh/setup-uv@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/