Skip to content

feat: enable Spark evals in CI - #489

Open
mattrossman wants to merge 6 commits into
mainfrom
mattrossman/ai-1413-enable-warp-for-evals-in-ci
Open

mattrossman wants to merge 6 commits into
mainfrom
mattrossman/ai-1413-enable-warp-for-evals-in-ci

Conversation

@mattrossman

@mattrossman mattrossman commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

Enables Spark evals in CI by running WARP inside Vercel Sandbox. Adds redaction of Spark URLs and credentials from published results and excludes Spark workspace and session archives from public artifacts.

The repository secrets CLOUDFLARE_WARP_CLIENT_ID and CLOUDFLARE_WARP_CLIENT_SECRET are configured using a service token provided from here.

CleanShot 2026-11-12 at 1 47 15 PM@2x

Both Spark and non-Spark experiments completed in CI. The Spark trace shows a migration, row update, and query working. Grading hit a known issue.

Once merged, this will allow us to run Spark evals by dispatching the workflow e.g.

gh workflow run eval-refresh.yml \
  -f eval=build-database-001-task-due-dates

Closes AI-1413

@vercel

vercel Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
evals Ignored Ignored Preview Nov 12, 2026 8:41pm UTC

Request Review

@mattrossman

Copy link
Copy Markdown
Collaborator Author

Note the sample scenario passed when we added it in #482. Running it in CI now hits a known Spark bug (Spark mixes up which columns belong to each table) which means reading all columns fails with tasks.instance_id whereas selecting columns by name works.

@mattrossman
mattrossman force-pushed the mattrossman/ai-1413-enable-warp-for-evals-in-ci branch from c19502d to a6843ba Compare November 12, 2026 19:18
@mattrossman

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-12T20:46:51.801864Z f21b378 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a6843ba10d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@mattrossman

Copy link
Copy Markdown
Collaborator Author

@codex review again 🙏

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: f21b37830e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@mattrossman
mattrossman marked this pull request as ready for review November 12, 2026 20:57
@mattrossman
mattrossman requested review from a team as code owners November 12, 2026 20:57

Copy link
Copy Markdown

@mattrossman https://supabase.slack.com/archives/C0C7XC4AV34/p1794516911579389?thread_ts=1794359901.275219&cid=C0C7XC4AV34

Me and Nikita were discussing this regression here. I already have the fix for it

Copy link
Copy Markdown

waiting for his approval to deploy

@mattrossman

Copy link
Copy Markdown
Collaborator Author

Thanks @pedrocarlo. FWIW that issue isn't a blocker for this PR, just wanted to highlight why the results looked that way.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants