Repository navigation
Commit 4eed4a3
authored
Fix nightly smoke dispatch picking a stale create-release run (#14949)
* Resolve latest nightly without filtered runs listing
A source=nightly dispatch with an empty run-id sometimes picked a
months-old create-release run. The workflow runs listing, when filtered
by branch and status, intermittently returns an outdated result set:
repeated identical calls returned runs from May, June or two weeks ago
instead of the latest. The May run had expired artifacts, which surfaced
as "produced none of the expected artifacts"; a run within the 90-day
artifact retention would instead have been tested silently as if it were
the latest nightly.
Listing without server-side filters and selecting the newest successful
main run in jq returned the correct run on every call. The listing is
still external state, so an auto-resolved run older than three days now
fails with a message asking for an explicit run-id rather than testing a
stale build. An explicit run-id bypasses the check.
* Compare nightly run age in seconds for the staleness check
Integer division to whole days truncated partial days, so a run just
under four days old passed the three-day limit.1 parent 5757cfc commit 4eed4a3
1 file changed
Lines changed: 15 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
267 | 267 | | |
268 | 268 | | |
269 | 269 | | |
270 | | - | |
271 | | - | |
272 | | - | |
273 | | - | |
274 | | - | |
275 | | - | |
| 270 | + | |
| 271 | + | |
| 272 | + | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
276 | 285 | | |
277 | 286 | | |
278 | 287 | | |
| |||
0 commit comments