Easen debugging, by adding some cpu information to testinfo.json

[Christian Ehrhardt ]

While more test specific debugging would have to be part of the test itself today we agreed that a bit of information about the CPU the test is running on would be helpful in general.

To keep it short, but useful eventually we agreed on #processors, cpu-model and flags from /proc/cpuinfo

So something like (and just that, no reason to report multiple times for multiple cpus):
processors: 4
model name : Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
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 eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap xsaveopt

[Christian Ehrhardt  (paelzer)]

As reference some part of our chat on 2nd of March 2016

[09:05] <pitti> cpaelzer: I'd rather expand it into the debci log
[09:06] <pitti> we have three links there already, adding more isn't helping confusion
[09:06] <cpaelzer> pitti: agreed
[09:06] <pitti> cpaelzer: indeed it's just replacing log.gz with result.tar in the URL
[09:08] <cpaelzer> pitti: IMHO the dbci log could take a plain /proc/cpuinfo, on s390x maybe also /proc/sysinfo - that would be great
[09:08] <cpaelzer> pitti: I also thought about lshw, but that is too heavyweight
[09:09] <pitti> cpaelzer: perhaps #processors and the model name
[09:09] <pitti> the full thing is quite big
[09:09] <cpaelzer> pitti: processor, model and flags of one of them?
[09:09] <pitti> ok
[09:09] <pitti> cpaelzer: mind reporting a bug against autopkgtest about that, as a reminder?
[09:09] <cpaelzer> I'll do

[Martin Pitt (pitti)]

http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=f2925b119

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopkgtest - 3.20.1

---------------
autopkgtest (3.20.1) unstable; urgency=medium

  * When testing click packages, don't regenerate all AppArmor profiles if
    /var/cache/apparmor/click-ap.rules already exists. That way the profiles
    can be pre-adjusted once in a testbed instead of once for each test run,
    which greatly speeds up iterations. (LP: #1553797)
  * Move SshRunner* tests from lxc to lxd.
  * NullRunner.test_tree_output_dir test: Only check for cpu_{model,flags} on
    x86 and ARM, as these need parsing adjustments on other architectures.
  * Disable lxd autopkgtest for now, this still needs some way to set a proxy.
  * lib/VirtSubproc.py, cmd_reboot(): Add workaround for dhclient hanging on
    reboot (see LP #1556175).
  * Fix regular expression for removing profile guarded dependencies on hosts
    that don't support build profiles.
  * adt-virt-lxc: Suppress lxc-copy's stdout in the "no btrfs" fallback case.
    (Closes: #818185)

 -- Martin Pitt <email address hidden> Mon, 14 Mar 2016 22:35:54 +0100