Repository navigation
fix(ci): take the two hosted-runner builds off the PR rail (#11946, option 3) - #11962
Merged
Merged
Conversation
…ption 3) The hosted 7 GB runner cannot build release/v3.8.51 in any profile: `Build App` (build.yml, push on every branch, full `build:release`) died in 19 of the last 30 runs — the branch tip included — with "The runner has received a shutdown signal" ~8 min into `next build`, swapfile and all; the advisory quality.yml build failed on 8/8 recent fork PRs with the same recipe; and `DAST smoke (PR)`'s backend-only build died ~7 min in before the server even started, hidden as a permanently red continue-on-error check. Together they painted every PR into release/** red with zero signal and, on build.yml, produced an artefact nothing downloads. - build.yml: workflow_dispatch only. The bundle is validated where a build fits — ci.yml `Build` on the self-hosted omni-build pool after every merge to main, and nightly-release-green.yml on the same pool for release/**. - dast-smoke.yml: pull_request into main only (plus workflow_dispatch to smoke a release branch by hand); main's tree still builds on the hosted runner in ~5.5 min. - quality.yml: the fork-only rationale of `Build (advisory)` updated to say why own-origin PRs no longer get a hosted build either. Behaviour unchanged. check:workflows --ratchet: 194 zizmor findings, baseline 194. check-workflows and backend-only-smoke-workflows suites pass. Trade-off stated in the PR: own-origin PRs into release/** lose a pre-merge build that was not succeeding anyway; the nightly rail files a base-red issue within a day if a merge breaks the build.
This was referenced Aug 29, 2026
This was referenced Aug 29, 2026
Bl0ck154
pushed a commit
to Bl0ck154/OmniRoute
that referenced
this pull request
Sep 20, 2026
…apw#11946, option 3) (diegosouzapw#11962) The hosted 7 GB runner cannot build release/v3.8.51 in any profile: `Build App` (build.yml, push on every branch, full `build:release`) died in 19 of the last 30 runs — the branch tip included — with "The runner has received a shutdown signal" ~8 min into `next build`, swapfile and all; the advisory quality.yml build failed on 8/8 recent fork PRs with the same recipe; and `DAST smoke (PR)`'s backend-only build died ~7 min in before the server even started, hidden as a permanently red continue-on-error check. Together they painted every PR into release/** red with zero signal and, on build.yml, produced an artefact nothing downloads. - build.yml: workflow_dispatch only. The bundle is validated where a build fits — ci.yml `Build` on the self-hosted omni-build pool after every merge to main, and nightly-release-green.yml on the same pool for release/**. - dast-smoke.yml: pull_request into main only (plus workflow_dispatch to smoke a release branch by hand); main's tree still builds on the hosted runner in ~5.5 min. - quality.yml: the fork-only rationale of `Build (advisory)` updated to say why own-origin PRs no longer get a hosted build either. Behaviour unchanged. check:workflows --ratchet: 194 zizmor findings, baseline 194. check-workflows and backend-only-smoke-workflows suites pass. Trade-off stated in the PR: own-origin PRs into release/** lose a pre-merge build that was not succeeding anyway; the nightly rail files a base-red issue within a day if a merge breaks the build.
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…apw#11946, option 3) (diegosouzapw#11962) The hosted 7 GB runner cannot build release/v3.8.51 in any profile: `Build App` (build.yml, push on every branch, full `build:release`) died in 19 of the last 30 runs — the branch tip included — with "The runner has received a shutdown signal" ~8 min into `next build`, swapfile and all; the advisory quality.yml build failed on 8/8 recent fork PRs with the same recipe; and `DAST smoke (PR)`'s backend-only build died ~7 min in before the server even started, hidden as a permanently red continue-on-error check. Together they painted every PR into release/** red with zero signal and, on build.yml, produced an artefact nothing downloads. - build.yml: workflow_dispatch only. The bundle is validated where a build fits — ci.yml `Build` on the self-hosted omni-build pool after every merge to main, and nightly-release-green.yml on the same pool for release/**. - dast-smoke.yml: pull_request into main only (plus workflow_dispatch to smoke a release branch by hand); main's tree still builds on the hosted runner in ~5.5 min. - quality.yml: the fork-only rationale of `Build (advisory)` updated to say why own-origin PRs no longer get a hosted build either. Behaviour unchanged. check:workflows --ratchet: 194 zizmor findings, baseline 194. check-workflows and backend-only-smoke-workflows suites pass. Trade-off stated in the PR: own-origin PRs into release/** lose a pre-merge build that was not succeeding anyway; the nightly rail files a base-red issue within a day if a merge breaks the build.
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
1 participant
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.
Opção 3 do #11946, adaptada ao que os dados mostraram
release/v3.8.51em nenhum perfil:Build Appmorreu em 19/30 runs (a própria branch incluída) ~8 min dentro donext build, com swapfile de 10 GB; oBuild (advisory)doquality.yml(mesma receita) falhou em 8/8 PRs de fork recentes; e oDAST smoke (PR)morre no passo "Build CLI bundle" (que é umnext buildbackend-only) ~7 min depois, antes de o servidor subir — escondido como check advisory permanentemente vermelho.ci.yml" não se aplica a PRs de release: oci.ymlsó roda emmain. Não há artefato para consumir lá.O que muda
build.yml(Fast Production Build)pushem toda branch,build:releasecompleto, artefato que ninguém baixaworkflow_dispatchdast-smoke.yml(DAST smoke (PR))mainerelease/**main(onde builda em ~5,5 min) +workflow_dispatchquality.ymlBuild (advisory)(fork-only) atualizado; comportamento igualTrade-off (explícito)
PRs de branch própria para
release/**ficam sem build pré-merge — que já não vinha passando. O bundle continua validado peloci.yml(Build, poolomni-build) em todo merge namaine pelonightly-release-green(mesmo pool) narelease/**, que abre issuebase-redem até um dia se um merge quebrar o build.Achado colateral (follow-up, não nesta PR)
nightly-schemathesis,nightly-llm-securityenightly-resiliencetambém fazemnext buildbackend-only emubuntu-latest→ muito provavelmente mortos na.51sem ninguém ver. Candidato natural ao poolomni-build(1×/dia, carga baixa) — decisão do dono.Validação
check:workflows --ratchetsem regressão (194/194);check-workflows.test.ts32/32;backend-only-smoke-workflows.test.ts6/6; prettier limpo.Closes #11946