cpu_topology script doesn't handle the word 'processor' in a CPU model name well

Bug #882161 reported by Brendan Donegan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Low
Unassigned
checkbox-certification
Invalid
Low
Unassigned

Bug Description

The cpu_topology script has a section of code to extract values of fields in /proc/cpuinfo that it is interested in. Unfortunately the logic gets tripped up where the word 'processor' is contained in the model name of a CPU, for example:

model name: Intel(R) Celeron(R) M processor 900MHz

Instead of using a simple 'string in string' statement it might be better to use string.startswith. I wouldn't go as far as saying regexes are necessary, but the possibility that the string might occur somewhere other than the start of the line needs to be guarded against.

This problem only appears to affect one old system at the moment so the importance of a fix is not that great.

Related branches

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Added a task for checkbox-certification as this needs to be backported to the SRU test suites for Lucid and Natty.

Changed in checkbox:
status: New → Confirmed
Changed in checkbox-certification:
status: New → Confirmed
Changed in checkbox:
status: Confirmed → Triaged
Changed in checkbox-certification:
status: Confirmed → Triaged
Changed in checkbox:
importance: Undecided → Low
Changed in checkbox-certification:
importance: Undecided → Low
description: updated
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

I will fix this for P in trunk and we will be able to use it during SRU testing and certification.

Revision history for this message
Daniel Manrique (roadmr) wrote :

Can this be marked Fix Released or Committed?

thanks!

Daniel Manrique (roadmr)
Changed in checkbox:
status: Triaged → Fix Committed
Changed in checkbox:
status: Fix Committed → Fix Released
Revision history for this message
Daniel Manrique (roadmr) wrote :

Is this still relevant for Lucid and Natty? If not, can we mark it invalid for checkbox-certification?

Changed in checkbox-certification:
status: Triaged → Incomplete
Jeff Lane  (bladernr)
Changed in checkbox-certification:
status: Incomplete → Invalid
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.