You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /proc/cpuinfo file is very variable across Linux architectures and even varies at runtime, as an install moves between CPUs (such as with a Linux live image) or even as you switch between Linux kernel versions (since newer ones might expose more info on very new hardware such as RISC-V). So the CPU speed test should probably not be run at build time. Instead the API should indicate that the function can return nothing/error at runtime and users of the API should be expected to handle that at runtime.
The CPU speed feature also isn't very useful, since at least on my Intel system, the cpu MHz field is different for each core and different each time that I read the /proc/cpuinfo file. So perhaps the CPU speed feature should be deprecated and later removed.
Hi,
From Debian rust sys-info package which FBTFS fail:
https://buildd.debian.org/status/package.php?p=rust-sys-info&suite=sid
I submit a patch to pass the tests case:
https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/295
But It seems very suboptimally.
So what is the best solution for such case?
The /proc/cpuinfo is below:
If no other options, I will send RP to pass the case that is the same patch for Debian.
The text was updated successfully, but these errors were encountered: