Cannot debug potential skipped tests based on udev information

Bug #974271 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
Brendan Donegan

Bug Description

the output of udev_resource should be made into an attachement so we can later verify that what udev says is what is true on the system.

For example, a system that failed to run miscellanea/virtualization_check. That is essentially a short script and it requires the following in the job description:

requires: cpuinfo.platform in ("i386", "x86_64")

Now, according to C3, the arch is amd64. But dmidecode and cpuinfo give no indication of architecture:

dmidecode:
Handle 0x0400, DMI type 4, 42 bytes
Processor Information
 Socket Designation: Proc 1
 Type: Central Processor
 Family: Xeon
 Manufacturer: Intel
 ID: C2 06 02 00 FF FB EB BF
 Signature: Type 0, Family 6, Model 44, Stepping 2
 Flags:
  FPU (Floating-point unit on-chip)
  VME (Virtual mode extension)
  DE (Debugging extension)
  PSE (Page size extension)
  TSC (Time stamp counter)
  MSR (Model specific registers)
  PAE (Physical address extension)
  MCE (Machine check exception)
  CX8 (CMPXCHG8 instruction supported)
  APIC (On-chip APIC hardware supported)
  SEP (Fast system call)
  MTRR (Memory type range registers)
  PGE (Page global enable)
  MCA (Machine check architecture)
  CMOV (Conditional move instruction supported)
  PAT (Page attribute table)
  PSE-36 (36-bit page size extension)
  CLFSH (CLFLUSH instruction supported)
  DS (Debug store)
  ACPI (ACPI supported)
  MMX (MMX technology supported)
  FXSR (FXSAVE and FXSTOR instructions supported)
  SSE (Streaming SIMD extensions)
  SSE2 (Streaming SIMD extensions 2)
  SS (Self-snoop)
  HTT (Multi-threading)
  TM (Thermal monitor supported)
  PBE (Pending break enabled)
 Version: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
 Voltage: 1.4 V
 External Clock: 133 MHz
 Max Speed: 4800 MHz
 Current Speed: 2667 MHz
 Status: Populated, Enabled
 Upgrade: Socket LGA1366
 L1 Cache Handle: 0x0710
 L2 Cache Handle: 0x0720
 L3 Cache Handle: 0x0730
 Serial Number: Not Specified
 Asset Tag: Not Specified
 Part Number: Not Specified
 Core Count: 6
 Core Enabled: 6
 Thread Count: 12
 Characteristics:
  64-bit capable

cpuinfo:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
stepping : 2
microcode : 0x13
cpu MHz : 2667.008
cache size : 12288 KB
physical id : 1
siblings : 12
core id : 0
cpu cores : 6
apicid : 32
initial apicid : 32
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 popcnt aes lahf_lm ida arat epb dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 5334.01
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:

So without a dump of what udev said during udev_resource, there's no way to verify that we've got a bug in the system, in the test, or where...

Related branches

Jeff Lane  (bladernr)
Changed in checkbox:
milestone: none → 0.13.6
Ara Pulido (ara)
Changed in checkbox:
importance: Undecided → Wishlist
milestone: 0.13.6 → 0.14
Changed in checkbox:
status: New → Triaged
summary: - udev_resource output should be made into an attachement
+ udev_resource output should be made into an attachment
Changed in checkbox:
assignee: nobody → Brendan Donegan (brendan-donegan)
Changed in checkbox:
status: Triaged → In Progress
Marc Tardif (cr3)
Changed in checkbox:
status: In Progress → Fix Committed
Ara Pulido (ara)
summary: - udev_resource output should be made into an attachment
+ Cannot debug potential skipped tests based on udev information
Changed in checkbox:
importance: Wishlist → Medium
Changed in checkbox:
status: Fix Committed → Fix Released
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.