[CentOS Stream 10] test_linux.TestSystemCPUFrequency.test_emulate_multi_cpu fails on aarch64

[hroncok]

Summary

• OS: CentOS Stream 10
• Architecture: aarch64
• Psutil version: 5.9.5, 5.9.8
• Python version: 3.12.1
• Type: tests

Description

I repeatedly see this test failure when I try to build the RPm package with python-psutil 5.9.8 (also happened with 5.9.5) for CentOS Stream 10 which we are boostrapping from Fedora 40. the failure does not happen in Fedora 40. Teh failure only happens on aarch64.

======================================================================
FAIL: psutil.tests.test_linux.TestSystemCPUFrequency.test_emulate_multi_cpu
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/psutil-release-5.9.8/psutil/tests/test_linux.py", line 931, in test_emulate_multi_cpu
    self.assertEqual(freq[1].current, 400.0)
AssertionError: 3000.0 != 400.0
----------------------------------------------------------------------

HW info from the failing CentOS Stream 10 builder:

CPU info:
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              32
On-line CPU(s) list: 0-31
Thread(s) per core:  1
Core(s) per socket:  32
Socket(s):           1
NUMA node(s):        1
Vendor ID:           APM
Model:               2
Model name:          X-Gene
Stepping:            0x3
CPU max MHz:         3000.0000
CPU min MHz:         375.0000
BogoMIPS:            80.00
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
NUMA node0 CPU(s):   0-31
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid


Memory:
              total        used        free      shared  buff/cache   available
Mem:      267695168     6172480   240045824     2025856    21476864   231431168
Swap:       4194240           0     4194240


Storage (chroot, cache_topdir):
Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/vg_aarch64--03-root  423G  8.1G  398G   2% /
/dev/mapper/vg_aarch64--03-root  423G  8.1G  398G   2% /

HW info from the passing Fedora 40 builder:

CPU info:
Architecture:                       aarch64
CPU op-mode(s):                     32-bit, 64-bit
Byte Order:                         Little Endian
CPU(s):                             12
On-line CPU(s) list:                0-11
Vendor ID:                          ARM
Model name:                         Neoverse-N1
Model:                              1
Thread(s) per core:                 1
Core(s) per socket:                 1
Socket(s):                          12
Stepping:                           r3p1
BogoMIPS:                           50.00
Flags:                              fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
NUMA node(s):                       1
NUMA node0 CPU(s):                  0-11
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; CSV2, BHB
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected


Memory:
               total        used        free      shared  buff/cache   available
Mem:        36860588     1330704     9229092        1068    26716420    35529884
Swap:        8388604         512     8388092


Storage (chroot, cache_topdir):
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda3       313G  4.2G  305G   2% /
/dev/vda3       313G  4.2G  305G   2% /

[sgallagher]

We are seeing this issue occur also on the ppc64le builders for RHEL 10.

[giampaolo]

It's unlikely I will be able to fix this since I cannot reproduce it. Do you think you can try to debug this yourself?

[hroncok]

Do you think you can try to debug this yourself?

If you give me hints on what to put to the code, I can try, but I don't have direct access to the builder machine.