dashboard reported number of failures does not match test's reported failures

[C de-Avillez]

See, for example, http://91.189.93.67/staging/sru/raring/version/3.7.0-5.13-generic/

* the 'virtual_i386_pae' line is reporting 3 failures, while Jenkins reports only one
* the 'virtual_amd64' line reports 4 failures, while Jenkins reports only one

and so on. Not all lines are wrong, though.

[Chris Johnston (cjohnston)]

On http://reports.qa.ubuntu.com/sru/raring/version/3.8.0-7.14-generic/ the virtual_amd64 is being imported twice (or the results are doubled) for some reason, I'm not quite sure why... You can see the correct results at:

https://jenkins.qa.ubuntu.com/job/sru_kernel-raring-virtual_amd64-kvm-virtual/17/api/json

[Chris Johnston (cjohnston)]

So it seems part of the problem is that there may be two runs for certain jobs in Jenkins.. For some reason, in the dashboard they are showing up only once... so.. https://jenkins.qa.ubuntu.com/view/SRU%20Kernel/job/sru_kernel-quantal-xen_amd64-amd_64-mga_g200ew/ has two runs on the 12th. The dashboard is only showing a link to run # 13, but displaying the results for #13 and #14. So 1 kernel can be part of multiple SRU Results, and because of this our data is being shown poorly. A few things could be desired here:

1) split the two jobs and show the results for each job separately
2) provide a link to each job in Jenkins - the issue with this though is that you don't know if one of the jobs had more/less failures than the other.