|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'm looking at a job splash page right now.
SA = 0
Dup code = 15
Comp warn = 0
Open Task = ~137
SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present),
when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings
e.g. builds 712-119 had
dup code = 15 all builds
open task = 137 all builds
comp warnings = ~5 for all builds
sa = ~155 all builds
comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state
sa = 0 warnings
dup = 15
tasks = 140
since the # of comp warnings was low (3-5) it may be including then correctly (when there are non-zero of them) its just hard to see (since there are 155 other counts) I changed the graph to 'distr by type' and it looks like comp warnings are on the x-axis