[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Wg-test-framework] Inclusion of Hardware details on osstest results pages



Hi Ian,

 

The problem I was referring to in the call was that it’s not immediately obvious what hardware we are running the test on from just looking at the job titles.

 

For example, (snapshot of an email from osstest-admin to xen-devel)-

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass

 

Upon further investigation, both the above tests seem to have failed on Intel systems. But that is not easily identifiable.

(/proc/cpuinfo output collected as part of the logfiles help. But someone who does not know where to look for may have problems here..)

 

Couple of suggestions-

 

1.       it might be nice to have processor vendor_id or processor model (at least) listed against the results for the jobs. Something like-

                    test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass (Intel(R) Xeon(R) CPU E5-240)
2.       I understand that there’s not a lot of space available on the report. So, if the above is not viable, an alternative solution may be to include the processor vendor, family/model names as part of the ‘Test control variables’ table of each job?
 
Thoughts?
 
I am open to any other suggestions as well.
 
Thanks,
-Aravind.
_______________________________________________
Wg-test-framework mailing list
Wg-test-framework@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-test-framework

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.