Repository navigation
Clarify watchdog exit telemetry and verify optional plug-in integration - #7
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.
An unexpected runnable-task stall could report
watchdog_observed: falsebecause that legacy field only recognizes expected watchdog tests. Preserve existing exit statuses and fallback decisions; addwatchdog_expectedand nullablewatchdog_triggeredso telemetry distinguishes normal, expected and unexpected exits. No BPF program, model, slice or default changes.Validation: Linux ARM64 compilation and three real QEMU exit cases passed. The intentional unexpected-stall loader returns status 1 as required. A fresh 250-second, eight-vCPU Lerwatt integration passed across all three clusters, including default standalone runs before and after, consistent shared maps, all 30 actuator values restored, no residual journal, zero throttle steps and zero bad writes. Source and binary hashes plus compact results are in
results/watchdog-status.The first integration collector failed on bpftool's raw byte-array key. That attempt remains failed, with its raw dump and cleanup evidence retained. Only semantic BTF decoding in the test tool changed; the complete fresh rerun passed with identical product binaries. Full raw records are archived locally with a published SHA-256 manifest.
This improves diagnostics, not the unresolved natural watchdog stall reported in the model-confirmation results. The unavailable-enum compatibility path was not exercised on this kernel. This single simulated-board integration establishes activation and cleanup, not prediction, throughput or energy superiority. Defaults remain unchanged.