Slowest CI tests

Args: [N] [#channel] — both optional. N defaults to 500. If #channel is omitted, just print the table and stop.

1. Gather the data

Run the script. With no build number it auto-picks the most recent finished build from a merged PR.

bun run ci:slowest                 # top 500 from a recent merged-PR build → TSV on stdout
bun run ci:slowest 47324 100       # specific build, top 100
bun run ci:slowest --json > /tmp/slow.json

The script (scripts/ci-slowest-tests.ts) does the heavy lifting:

• Lists test-bun jobs from bk build view <N>, skipping retried: true.
• Fetches each job's raw_log_url directly with Authorization: Bearer $BUILDKITE_TOKEN. Do not use bk job log — it hangs indefinitely on some Windows/alpine jobs.
• Caches logs to $TMPDIR/bun-ci-logs-<build>/ so re-runs are instant.