Repository navigation
Conversation
The Android/OpenHarmony ethtool path can truncate speeds above 65535 Mbps. Compare NetworkInterface.Speed with /sys/class/net/<iface>/speed when the kernel reports a high-speed link; skip interfaces where sysfs is unavailable.
dotnet-policy-service
Bot
added
the
community-contribution
|
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. |
|
Tagging subscribers to this area: @karelz, @dotnet/ncl |
|
@dotnet/ncl could someone take a look at this regression test when you have a moment? It is the follow-up to #136194; CI is green (74 pass, 0 fail). The test only asserts when Note This comment was drafted with AI assistance (agent tooling) under the author's direction. |
|
We usually add the regression test in the same PR that lands the fix, having now 2 PRs and one issue makes things messy and chaotic to understand what is going on |
|
Moved the regression test into #136194 ( Note This comment was drafted with AI assistance (agent tooling) under the author's direction. |
Summary
Adds a conditional regression test for the Android/OpenHarmony ethtool speed truncation fixed in #136194.
NetworkInterface.Speedis compared with/sys/class/net/<iface>/speedonly when the kernel reports more than 65535 Mbps; interfaces where sysfs is unavailable or the PAL reportsSpeed <= 0are skipped.This is hardware-only coverage: the bug needs a NIC above 65535 Mbps, and CI machines do not have one. A deterministic native harness is tracked in #136353.
Merge after #136194.
Note
This PR was drafted with AI assistance (agent tooling) under the author's direction.