Fix nightly inference, extension, VOPR, and CI cache regressions - #826
Merged
Merged
Conversation
Contributor
Author
|
/ci run 4551c51 |
Contributor
Author
|
/ci run f811469 |
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.
Fix the code and test failures exposed by nightly run 35511643401, following the merge of #821.
Validation: targeted inference unit tests; PDF ReleaseSafe tests and OCR E2E; 38 extension/ABI tests and all five extension E2E tests with Wasmtime v45; 21 targeted inference E2E cases with CI memory budgets; clean speaker-model download; model-helper regressions and six cache-pruning tests; Linux cross-build verification of self-hosted and LLVM artifact layouts; storage/provider/full-cluster VOPR and resource-pressure replay; secret-backend tests. The final production VOPR ReleaseSafe smoke gate passed: 18/18 build steps and both 15-test suites, including baseline and bounded-lifecycle exact replay.
The build-cache job separately lost contact with its runner. Its logs were unavailable; this PR does not claim a code fix for that infrastructure failure.
The rename/name-reuse regression failed against the previous binary in both standalone and distributed modes, then passed with the fix. The production ReleaseSafe server build passed. CI requested for
f811469b0547ae3560699ba20a78e532104f8ca7.