Repository navigation
P9 isolated Windows trial: exact ARSAS+ARIEC SHA, nonrelease four-RCB validation - #767
Draft
masarray wants to merge 1 commit into
Conversation
Reuse vetted nonpromotion FAST DEV workflow, preserve P8 fallback, stage P9-specific artifact name and engine/manifest verification without changing mainline engine lock.
Owner
Author
|
P9 exact-SHA software milestone — CI verified, NOT physical acceptance (2026-11-05).
What this DOES NOT establish: SG7 physical recovery to 77/77 and 4/4; original SIEBCU first-attempt TCP/ACSE failure cause; lossless SOE continuity or physical endurance. CI is a synthetic/integration build gate, not IEC 61850 interoperability FAT. Keep PRs Draft and issue #707 OPEN pending actual field evidence. No cyclic MMS polling or spontaneous control/RCB ownership changes were introduced. |
Owner
Author
Final dual-path validation (exact ARSAS source, 2026-11-05)
Code and nonrelease Windows trial packaging gates are fully green at source |
This branch has not been deployed
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.
P9 exact-SHA Windows integration candidate (nonrelease)
Immutable provenance
c7b7c68c6bf59a53082c09dd7584ea3d5312429e(consumer PR P8 field fix: SIEBCU first-connect retry, exact two-bit display and false no-report warning #766), which already passed canonical Windows CI and IO validation.58d22be43d93d1d439df04a99ba935a7ec45cd4c(P9 engine PR #200); engine CI #41980603839 1,292/1,292 PASS.f75e323e9f8443aa20e0a3818a1d5d77255b2c0f.main, integrated RC and stable v1.6.42 untouched.Scope
Use the existing label-gated, explicitly nonpromotable
ci-p1-shadowreporting integration pipeline; update only the trial manifest and add backward-compatibleP9-specific artifact filename. Fail closed if the manifest's engine SHA disagrees with exact checked-out engine; preserve legacyP8naming for a P8 manifest. The test workflow includes Windows solution build, focused reporting regression, native bridge CTest, single EXE build, executable smoke, and exact SHA256 manifest.No premature acceptance
CI success will prove build/smoke and synthetic correctness, not SG7 physical 77/77 or 4/4, first-click reliability on SIEBCU, or lossless SOE. Keep this PR Draft, test artifact nonrelease, and SG7 issue #707 Open. No hidden cyclic MMS polling, blanket RCB ownership mutation, or automatic control is authorized.
Please keep the separate P8 and P9 source branches intact to avoid cross-thread collisions.