Skip to content

Distinguish completed emulator configuration checkpoints - #12

Merged
erikleblansch merged 7 commits into
feature/native-dps-jni-20261021from
fix/native-dps-kvm-configuration-20261022
Oct 22, 2026
Merged

erikleblansch merged 7 commits into
feature/native-dps-jni-20261021from
fix/native-dps-kvm-configuration-20261022

Conversation

@erikleblansch

@erikleblansch erikleblansch commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

The reviewed PR #13/#14 stack is integrated here with exact tested tree 714e806a71325ffab27e5b16e4e785305b73557b. Original trial 39844370003 passed the eight synthetic Android/JNI cases, cancellation controls and owned cleanup. Independent review verified artifact SHA-256 234b28aa81eca4ea68a9148845096b7a132f1976b5fbe547c24172ff7ce57a65 and recomputed the completed-emulator configuration result true while strict raw comparison remains false. Actual Linux 7.0 was exercised; 6.17 remains source-only. Physical sensors, accuracy, main Map navigation and app-identity attestation remain outside this fixture.

Earlier failures remain failed under their original contracts. Original KVM criterion rationale and evidence are preserved below.

A completed Android emulator can leave only /dev/kvm ctime/mtime different while the actual device identity, permissions, ACL, group and other host configuration remain unchanged. This candidate distinguishes these checkpoint results, retains every raw snapshot, and keeps strict metadata checks for all quiet, cancellation and incomplete-work controls.

Source: 058532d8569759c7cbcb63d7546b7c006574b8b7, tree f4a75f2f9bc06252dcacec9d86f3eb451dc6a978, based on PR #10 head f3296c21f9787cb760e561954652158c7b21601d. Only four reviewed files change. This is separate from the diagnostic-only PR #11.

The closed comparator validates complete snapshots before comparison. Only successfully completed emulator work with no original failure or cancellation can use configuration equality; every authority/identity/ACL field and all other baseline components remain checked. Phase schema 2 and final receipt schema 3 report raw equality and configuration equality separately. Parent recomputation rejects false child claims. No raw metadata is normalized or used as a new baseline.

Independent Sol source review passed: frozen 46,096-byte full-index diff SHA-256 aef9f480ddb603de1fa1c85112ec45389f09e122667c0f8f11c944b1ece8db10, 13 focused inert tests, source gate and diff check; author reports all 105 inert tests pass. 92 of 93 old test ASTs are identical; the remaining malformed-input test is strengthened. Workflow, pins, lifecycle/query-only controls, eight Java tests and JNI sources remain unchanged. Hosted source 39699608967 passes 105 tests and components 39699608966 passes 31. Both actual checkout logs and GitHub commit metadata bind test merge 4dc975579d64abe6ff97c27f814343eb0298c94c to the exact reviewed tree and expected two parents. Source log SHA-256 14220a4577c3d4a2e1bcb63b657b9cf99b538f903c7a72a4b1888ce33147bf40; component log SHA-256 cd8ad060eacd9e7be6554ab7ac5bcf7430d0eb58120876d93848c575af360bda. Exact-source full trial 39699719553 finished with failure. Emulator/native-JNI receipts report successful completed work and the owned process/state cleanup reports completion, but the outer IPv6-route fingerprint differs. KVM configuration matches with raw timestamp changes retained; firewall differences are classified as counters-only. The final host-configuration checkpoint is not accepted and cleanup reports HOST_BASELINE_UNCONFIRMED. The IPv6 change is unresolved; no normalization, new baseline, full host-safety or physical-positioning acceptance is inferred. Artifact 12392318675 is 98,619 bytes, SHA-256 6170ba89686be41fabb75d1121bfda58357646be3165426b5caaa02c5006eb34; original log SHA-256 f50db96e4e2f66969a86120828c35f4f94a637569891946aaf854dd14f758f52. Keep this candidate unmerged pending a source-backed resolution and reviewed evidence; no repeat trial has been dispatched.

Historical full trial 39694570310 passed all eight Android tests and process/state cleanup but failed the strict KVM timestamp guard. Minimal control 39696546767 completed one empty VM creation/close, observed timestamp-only changes and retained its strict failed verdict; it ran no Android workload. Neither result is relabeled. This new completed-work criterion cannot exclude transient permission/ACL changes followed by restoration and does not identify the metadata-changing actor. Actual navigation, sensors, physical positioning and confidential execution remain unproved.

@erikleblansch
erikleblansch marked this pull request as ready for review October 22, 2026 20:12
@erikleblansch
erikleblansch merged commit 0f473e8 into feature/native-dps-jni-20261021 Oct 22, 2026
3 checks passed
@erikleblansch
erikleblansch deleted the fix/native-dps-kvm-configuration-20261022 branch October 22, 2026 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant