Excess drift reporting#2
Merged
Merged
Conversation
borland
force-pushed
the
orion/excess-drift
branch
from
c390455 to
e3d8901
Compare
rosslovas
reviewed
Jul 12, 2026
|
|
||
| - name: Publish AOT exe | ||
| if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' | ||
| #if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch' |
Collaborator
Author
There was a problem hiding this comment.
Yes, just so I could publish a pre-release and use it from TeamCity. Not meant to merge to main though, I'll roll back
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
2 participants
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.
Microsoft have asked us if we can capture the state of VM's experiencing excess drift.
Claude implements the following changes, in this PR.
Add a new event to log, with EventId 1500, and message "Excess Drift Detected"
Update the monitoring logic so that if it observes three consecutive measurements where the drift is more than 60 seconds away from "true" time, it logs this event, and also writes a new file EXCESS_DRIFT to the same folder as the log output.
Note: Drift can be either positive or negative 60 seconds away; both are considered errors
Note: A "good" measurement after an excess one resets the logic; we need three CONSECUTIVE measurements to trip the state