fix(ci): pin Application CI hosted runner image - #1518
Closed
seonghobae wants to merge 2 commits into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause under investigation
Fresh exact-head evidence on the email-writing dependency root #1322 showed Application CI run
33518773598stuck before checkout on both product jobs: backend job99892417917and frontend job99892418052remainedqueuedwithrunner_id=0andsteps=[]. Protecteddevelop@042b0c70531b229af3acbd0421a2f23098d848b3selected the floatingubuntu-latestimage for both jobs.A central runner incident (
ContextualWisdomLab/.github#712) had same-class observations suggesting explicit hosted-image selection was worth testing. This PR therefore isolates that hypothesis without weakening any gate.TDD / experiment
RED commit
9db6eecdba1901683de26ca2cf31f7964a6bccdaadds a repository-level regression requiring both Application CI jobs to use the explicit supported image. It fails against the protected-base workflow, which saysubuntu-latest.Implementation commit
df877204c1c9fa69153229c52976a9c3e7372129changes only the tworuns-onselectors toubuntu-24.04.Current exact-head evidence does not prove the hypothesis. Application CI run
33528210732generated backend job99924366568and frontend job99924367053with labels exactly["ubuntu-24.04"], but repeated live reads still show bothqueued,runner_id=0,steps=[], before checkout. This means explicit label selection alone is currently insufficient to restore runner acquisition in Naruon. The central owner path has been updated with this A/B evidence. Do not describe this PR as a successful runner repair unless actual acquisition/checkout evidence appears.Writer/overlap boundary
External Claude-owned PR #1502 also edits
.github/workflows/app-ci.yml, but its current patch does not change eitherruns-onselector; it adds PostgreSQL service/configuration and removes the PR branch filter. This PR intentionally excludes every #1502 behavior and carries only the runner-selection regression plus selector experiment. If #1502 merges first, ordinary-restack/reconcile this PR onto fresh protecteddevelop, preserve only still-justified unique delta, and regenerate exact-head evidence. Do not copy or rewrite the external branch.Acceptance / disposition
Keep this lane only while it supplies useful non-duplicative runner-selection evidence. It is mergeable only if:
developaccepts a qualifying post-last-push approval, with no self-approval or bypass.If central repair proves the selector change unnecessary or current evidence continues to show no causal benefit, close/supersede this experiment with its exact evidence rather than merging a speculative workflow preference.
Related: ContextualWisdomLab/.github#712.