fix(pr-gate): greptile — exclude long_context_1m from PR gate

The long_context_1m row sends a ~210k-token prompt to Sonnet + Opus
across five providers, costing ~$19 per run by the row's own cost
note. That price tag is acceptable on the daily cron (a single run
per day) but not on a per-PR merge gate, where a busy main branch
would burn hundreds of dollars/day on this one row alone.

Exclude it via --ignore=tests/claude_code/long_context_1m. The
daily cron in tests/claude_code/cron_vm/run_daily.sh continues to
exercise the row and publish the cell to the matrix.
This commit is contained in:
mateo-berri 2026-05-19 02:48:59 +00:00
parent 2ff8bc46b1
commit 88a795bfcc

View file

@ -2450,6 +2450,16 @@ jobs:
# writes to the working directory and no CI step collects
# them, so reviewers can't pull the per-cell pass/fail
# breakdown when a red gate needs triage.
#
# `long_context_1m` is excluded from the pytest run:
# the row sends a ~210k-token prompt to Sonnet + Opus
# across five providers (~$19 / run by the row's own
# cost note). That price tag is acceptable on the daily
# cron but not on a per-PR merge gate -- a busy main
# branch would burn hundreds of dollars/day on this one
# row alone. The daily cron in
# tests/claude_code/cron_vm/run_daily.sh still exercises
# it and publishes the cell.
env -i \
PATH="$PATH" \
HOME="$HOME" \
@ -2467,6 +2477,7 @@ jobs:
--ignore=tests/claude_code/_builder_unit_tests \
--ignore=tests/claude_code/_publisher_unit_tests \
--ignore=tests/claude_code/_pr_gate_unit_tests \
--ignore=tests/claude_code/long_context_1m \
--junitxml=test-results/junit.xml \
--durations=10
no_output_timeout: 30m