My DuckDB Extension PR Sat Red for Eight Weeks. The Bug Wasn't What the CI Said.

On May 10 I opened a pull request to add gpudb— a GPU-accelerated DuckDB extension that runs on both NVIDIA CUDA and Apple Silicon Metal— to the DuckDB community-extensions registry. Then it sat. One red check, no maintainer comment, eight weeks of silence. The failing job was called linux_arm64, so of course I spent the first hour convinced I had an ARM problem. I didn't. The CI was lying to me— not maliciously, just structurally. Here's what actually broke, and how a fleet of AI agents took it from red to green on all four platforms in about seventy minutes.

The misdirection: a platform name is not a diagnosis

The only red job was linux_arm64. Every instinct says "cross-compilation, ARM toolchain, some aarch64 quirk." But the actual error, buried in the log, was three words:

make: *** No rule to make target 'set_duckdb_version'

Enter fullscreen mode