Repository navigation
ci(vold): qualify original pdx235 vold byte-for-byte before timeout patch - #161
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Stage 1 only — prove a byte-identical unmodified
voldThis PR is intentionally independent of draft vold timeout module #157. It does not include or activate an exFAT timeout patch, vold injection, signing keys, release permissions, or scheduled OTA selections.
/system/bin/voldas a reference.voldwithlineage_pdx235-userdebug/m vold. Reject dirty or mismatched project revisions.baseline-report.jsonrecords both SHA-256s, byte sizes, difference offset, manifest and source identity. Fail if even one byte differs.modos-lineage-largerunner label, guarded cleanup and a report-only artifact.Important: CI unit tests verify the baseline workflow contract, not a real Android build. A real baseline requires a large, trusted self-hosted runner with
MODOS_VOLD_BASELINE_RUNNER_READY=trueandMODOS_LINEAGE_LARGE_SCRATCHconfigured. Until those are provisioned, the manual workflow cannot establish binary reproduction. The workflow is intentionally a manual trigger onmain, so it becomes runnable after this safe infrastructure-only PR merges.Once the actual CI run produces a independently reviewed
byte_identical: truereceipt, return to PR #157 for separate patched build, nonpublishing OTA, device tests and only then potential scheduled deployment. No force-publish is authorized by this PR.Provisioning and acceptance: docs/vold-baseline-ci.md.