checking android cpu info files#131129
Conversation
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
/azp run runtime-androidemulator, runtime-android |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Pull request overview
This change adds runtime diagnostics to the NativeAOT Exceptions smoke test (CPU count, server GC state, Android detection, and /sys/devices/system/cpu/* contents). It also introduces an Android-specific early exit in Main, which changes the test’s behavior and expected exit code semantics.
Changes:
- Print
Environment.ProcessorCount,GCSettings.IsServerGC, andOperatingSystem.IsAndroid(). - Attempt to read and print
/sys/devices/system/cpu/{possible,present,online,offline}(with error handling). - Return
42immediately on Android.
|
/azp run runtime-androidemulator, runtime-android |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
Comments suppressed due to low confidence (1)
src/tests/nativeaot/SmokeTests/Exceptions/Exceptions.cs:54
- This early return makes the test exit with code 42 on Android before executing the rest of the exception coverage, which contradicts the later Android-specific behavior in this test (it currently returns Pass on Android at the end). If the goal is just to print diagnostics, avoid changing the test outcome.
if (OperatingSystem.IsAndroid())
{
return 42;
}
|
Tagging subscribers to this area: @JulieLeeMSFT, @VSadov |
|
/azp run runtime-androidemulator, runtime-android |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
|
/azp run runtime-androidemulator, runtime-android |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
No description provided.