Skip to content

Release blocker: helper-runtime prelink stale again (15 ext/dom units) — user_release_ready red #24356

Description

@PurHur

Summary

./script/release-readiness.sh --json reports user_release_ready: no. First failing gate:

helper-runtime-prelink: FAIL
check-helper-runtime-prelink.php --strict
→ x86_64-linux — 244 fresh, 15 stale, 0 broken

All 15 stale units are under ext/dom/ (DomC14NJitHelper, DomLoad*, DomSave*, VmDomInstanceInvoke, …). Same class of defect as #24302 / #24336 (committed corpus skipped → cold compiles pay full emit).

Repro

./script/docker-exec.sh -- bash -lc 'php script/check-helper-runtime-prelink.php --strict'
# expect: N fresh, 0 stale, 0 broken

./script/release-readiness.sh --json
# expect: helper-runtime-prelink status ok; user_release_ready yes (other gates equal)

php-src / reference

N/A — compiler tooling / committed helper-object cache (prelinked/helper-runtime/), not Zend semantics.

Done when

  • php script/emit-helper-runtime-object.php --prelink (Docker) refreshes stale units from live fingerprints
  • php script/check-helper-runtime-prelink.php --strict → 0 stale
  • ./script/release-readiness.sh --json → helper-runtime-prelink: ok (and user_release_ready: yes if no other gate fails)
  • No restamp without rebuild — publish real unit objects (artifact honesty)

Related

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:toolingTooling / CI / docsbugSomething isn't workingimplementation-readySpec complete: repro, php-src ref, done-when — safe for workers to claimphase-0:FoundationPhase 0 – foundation & DevEx

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions