You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a PR has already run the full untrimmed sweep (`full-sweep-enabled` label),
184
+
a maintainer can avoid running the same sweep again after merge by leaving a
185
+
PR comment before merging:
186
+
187
+
```
188
+
/reuse-sweep-run
189
+
```
190
+
191
+
That reuses the latest successful `run-sweep.yml``pull_request` run for the
192
+
PR's current head SHA. If the PR was rebased or had to merge `main` after the
193
+
successful sweep — so the current head no longer has a matching run — pin the
194
+
source run explicitly:
195
+
196
+
```
197
+
/reuse-sweep-run <run_id>
198
+
```
199
+
200
+
The comment is the reuse authorization, so adding it does not trigger or cancel
201
+
a PR sweep. On the push-to-main run, `run-sweep.yml` resolves the merged PR
202
+
from the merge commit, verifies the source run is a successful `pull_request`
203
+
`run-sweep.yml` run for the same PR, downloads the ingest-relevant artifacts,
204
+
validates that `results_bmk` covers the merge run's expected benchmark matrix,
205
+
and uploads them as `reused-ingest-artifacts`. The normal database ingest then
206
+
publishes those artifacts with the merge run's changelog metadata.
207
+
208
+
Only comments from `OWNER`, `MEMBER`, or `COLLABORATOR` users authorize reuse.
209
+
The most recent matching comment wins, so a maintainer can supersede an earlier
210
+
pin by leaving a new `/reuse-sweep-run [<run_id>]` comment.
211
+
212
+
Reuse fails closed: if the comment is present but the `full-sweep-enabled`
213
+
label, source PR run, or artifacts cannot be validated, the push-to-main
214
+
workflow fails instead of falling back to a cluster sweep. Without the comment,
215
+
the push-to-main workflow runs the normal full sweep.
216
+
181
217
## Validation Architecture
182
218
183
219
The benchmarking system uses a strict validation methodology to ensure correctness at every stage. This is implemented in `utils/matrix_logic/validation.py` using Pydantic models.
0 commit comments