stress/cpu_stress_ng_test failed with STRESS_NG_CPU_TIME=60 on Alder Lake machine

Bug #2012482 reported by Dirk Su
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
New
Undecided
Unassigned
OEM Priority Project
New
High
Dirk Su

Bug Description

[Summary]
run stress/cpu_stress_ng_test with STRESS_NG_CPU_TIME=60 on Alder Lake machine

[Cause]
stress_cpu function add 10% to runtime which not seems enough for machine have more cores

Revision history for this message
Dirk Su (dirksu) wrote :
tags: added: oem-priority originate-from-2008986 somerville
Changed in oem-priority:
importance: Undecided → High
assignee: nobody → Dirk Su (dirksu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.