Skip to content

regen-on-ci: branch regens first (master cache runs cancel and yield) - #177

Merged
thejackshelton merged 14 commits into
masterfrom
regen-ci-priority
Oct 5, 2026
Merged

thejackshelton merged 14 commits into
masterfrom
regen-ci-priority

Conversation

@thejackshelton

Copy link
Copy Markdown
Contributor

What changed (.github/workflows/regen-on-ci.yml only):

  • Concurrency groups:
    • Master's cache runs (push) share one group, regen-on-ci-master-warm, with cancel-in-progress, so only the newest master run matters.
    • Branch runs get a group per branch and per label. Before, every pull_request labeled event joined its branch's group, so any other label, such as fulltest, replaced a queued regen run.
  • Branch regens first: the macOS runners are one pool of 5 jobs, and GitHub has no job priority. So a master cache run yields: its resolve job counts regen-on-ci runs that are not pushes and are queued, waiting, pending or in progress. If there are any, it records mode=skip and runs nothing; the next master push warms the cache instead. The resolve job gets actions: read to list the runs.

Regen time now (per-step seconds from the rounds' last-run.json):

run round wall steps (seconds)
branch seld-r2-c 37275532666 (40 min) chrome-1 20.5 min pixel-capture 319, wpt 182, vectors 172, hit-capture 154, dpr-capture 152, native-gen 150, break-capture 129, capture 126, profile-rows 117, media-sweep 95, dpr-vectors 69, north-star 56, anim-capture 38; the rest are under 15
host-1 5 min lanes-host 264
chrome-2 3.7 min profile-rows 116, north-star 41
sweep 9 min tw-sweep 448
master 37283930399 (37 min, after #161) chrome-1 19 min pixel-capture 296, ua 241, wpt 144, native-gen 141, dpr-capture 132, hit-capture 131, profile-rows 99, break-capture 95, vectors 94, media-sweep 65
host-1 8 min lanes-host 429
sweep 3.4 min tw-sweep 138

Tests: actionlint is clean. The yield takes effect on the first master push after this lands.

🤖 Generated with Claude Code

thejackshelton and others added 14 commits October 4, 2026 20:41
…llbar-color and ::-webkit-scrollbar rules

The reviewed list (profiles/not-applicable-native.ts) is accepted on ios and android with an info diagnostic
(DRAGON_NOT_APPLICABLE_NATIVE) and nothing emitted; web still refuses it. querySupport answers not-applicable on
native; the north-star accounting counts these declarations on their own and leaves them out of the denominator.
A native target that compiles only because every web refusal is not applicable on native is recorded as na-native,
counted on its own; any other native-compiles-but-web-does-not result still throws.
…g colours, exact property windows in the sweep, resolved query

A ::-webkit-scrollbar* rule is not applicable only when its block holds nothing refused or nested and only background-color,
a plain-colour background, border-radius, border-color or color, with no transparent or alpha-0 colour; scrollbar-color only
when auto or two visible colours. The sweep explains a later refusal only through a pseudo-element item. A resolved query of a
listed property on a native target answers not-applicable.
…s stay refused on native (deferred to na-native-scrollbar)

A resolved query validates its element before answering not-applicable; the sweep explains a web refusal only at an item's
own span; docs/api.md notes the new SupportAnswer member.
…s to diagnostics/codes/na-native.ts (HOTSPOT-SPLIT registry)
…regens; per-branch, per-label groups so other label events never displace a queued regen
NA-NATIVE: not applicable on native, a third verdict (cursor)
@thejackshelton
thejackshelton merged commit 65e91d9 into master Oct 5, 2026
5 checks passed
@thejackshelton
thejackshelton deleted the regen-ci-priority branch October 5, 2026 15:32
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.

1 participant