Repository navigation
test(profile): expose locked native package smoke - #54
Merged
Merged
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.
Native package ownership and restart proof is now reachable through
test rust-release-packageunder the existing workspace lock. The command invokes the selected persisted Harness smoke script, supplies the current clean Rust revision automatically, and passes package version/CPU plus optional ownership/WebUI proof flags. Release inputs stay under OUTPUT, child scratch and retained reports use managed output directories, and selected Builder/Rust/Harness/Tooling revisions must remain clean and unchanged.The existing Harness owner retains package checksum, SBOM, version/CPU, local transfer, restart, launch and teardown responsibilities. This adapter builds or stages no operator runtime and adds no process framework. Its source receipt remains failed if selected sources change even when the runner produced a passing report. Both existing Windows/Linux direct-owner selections now include the focused adapter tests, preserving all mandatory commands and the source-symlink tests from merged #53.
Validation: the supported scoped Builder runner passed 63 tests with no failures/errors/skips; normal push hooks on the final rebased source passed the same CLI/admission owners plus privacy, hygiene and workflow lint. Actual package/runtime proof is pending a package built from the selected clean Rust candidate; mocked admission tests do not establish that proof.
Related to emulebb/emulebb-rust#247.
--verify-profile-ownershiprequires emulebb/emulebb-build-tests#105; ordinary native smoke uses the existing script interface. Based on merged #53; the selected source and source-material cache fix remain intact. Example after qualifying a matching package:python -B -m emule_workspace test rust-release-package --workstream profile-ownership --release-dir <OUTPUT/release/candidate> --release-version <version> --target-os windows --platform x64 --verify-profile-ownership.