Repository navigation
Architecture status: F´ components built and tested - #15
Merged
Merged
Conversation
…nd unit-test counts; spare and standby hooks
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
1 participant
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.
Layer 1 evidence and parts now name the F´ components (mruspace/flight#6): RedundancyManager, HealthRegistry and ReplicaHost are built, with 37 unit tests and a system test that gives the demo's counts on the bench schedules. Counts from CI: 9 Kani proofs, 21 scenario checks (Linux). Layer 1 stays at Prototype: nothing has run on flight hardware. The inventory and power-accountant rows name the new hooks (admit a spare, standby) without moving their status.
npm run checkpasses (0 errors, 101 e2e tests, Lighthouse). Merge after mruspace/flight#6, so the link to fprime/ resolves.