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
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552129 Title: Easen debugging, by adding some cpu information to the dbci log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1552129/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
