[JIRA] (JENKINS-7781) "Test Statistics Grid" double counting aggregated tests
Title: Message Title Tobias Gruetzmacher assigned an issue to Unassigned Jenkins / JENKINS-7781 "Test Statistics Grid" double counting aggregated tests Change By: Tobias Gruetzmacher Priority: Major Minor Assignee: Marco Ambu Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests I don't understand the behaviour either, but you said that this also happens when displaying the test results in jenkins. This is important because we don't do any special processing with the test results and we get them directly from jenkins APIs. Can you please show me also the standard test result for the main job? Does it show the 5 missing tests? Need to check about the disabled job: do you think we should include it as well in the total count? If not we could "mark it" in a special way so that it does not cause confusion in the table? What version of the dashboard-view plugin are you using? 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
ellisonch commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests On the c-semantics project page, it says "Latest Test Result (85 failures / ±0)" without double counting that. If I click that link, it gives me "5 tests", which is correct for the main job. If I click to "aggregated test result" on the left, I see good numbers. 85 failures, 1554 total tests, 526 unit tests, 33 integration, 777 torture, 127 third party, 91 negative, and N/A csmith. It does leave out the 5 tests in the main job, but it doesn't double count anything. It's been so long since my initial report that I'm not sure what I used to see. We're using Jenkins 1.444 and Dashboard View 2.1 now. I won't be able to upgrade or try installing different things because I'm leaving the group. I do know that the double counting has happened pretty reliably over the past few years. Hope this helps! 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests Is this still an issue? It seems that the dashboard is behaving correctly anyway because you said: In actuality, my main job has 4 tests, and the three sub jobs have 684 tests in total. dashboard-view is reporting that the main job has 684 tests (so it is counting the subs, but not its own), in addition to the sub jobs, for a total of 1368 tests. So if jenkins is not reporting the 4 tests in the main job either, then I don't think we are doing anything wrong in the dashboard portlet. 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu resolved JENKINS-7781 as Not A Defect Test Statistics Grid double counting aggregated tests I'm closing this one. Reopen it, if still an issue. Change By: Marco Ambu (17/Jul/12 1:54 PM) Status: Open Resolved Resolution: NotADefect 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
ellisonch reopened JENKINS-7781 Test Statistics Grid double counting aggregated tests It still seems like an issue to me. I will try to attach more information. Change By: ellisonch (17/Jul/12 2:59 PM) Resolution: NotADefect Status: Resolved Reopened 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
ellisonch updated JENKINS-7781 Test Statistics Grid double counting aggregated tests Change By: ellisonch (17/Jul/12 3:00 PM) Attachment: stats.png 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
ellisonch commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests I've added an attachment showing what I mean. If you add up all the child tests except for the csmith-tests, you get 1554. This number is being reported for c-semantics as well. So these tests are double counted in the 3669 total (which makes the % success total meaningless). Furthermore, the 5 tests that belong to c-semantics itself are not counted at all in these numbers. Finally, the csmith-tests are not being double counted, perhaps because the job is disabled. I don't really understand any of these behaviors. Let me know if you need more info. 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
