Repository navigation
chore: Add logging to investigate issue that different CPU frequency is reported on windows(arm64) - #3298
Closed
filzrev wants to merge 1 commit into
Closed
chore: Add logging to investigate issue that different CPU frequency is reported on windows(arm64)#3298filzrev wants to merge 1 commit into
filzrev wants to merge 1 commit into
Conversation
Contributor
Author
|
Close this PR. Because it can be reproduced on forked CI side. Output of it looks like CPU frequency is correctly recognized on Windows side. |
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.
This PR modify
CpuDetectorTestsand add logging to investigate #3285.By this logging, it can confirm what's CPU frequency is shown on
systeminfocommand.Cobalt 100processor is expected to be 3.40 GHz.But sometimes it's reported as
2.85 GHzon registry-based implementation.It might be difference between registry/CIM
Data Sourceof CPU frequencyData Update Timing(Registry info might not be updated after OS boot)