-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JENKINS-33952] "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed #215
Comments
Resolved in 2.9.8 |
2.9.8 |
I tested again with version 2.9.9 |
What plugin are you using to run/tabulate the test statistics? The Dashboard view is pretty dumb; it just reports whatever the test result actions from the plugin report. I can try and confirm/diagnose, but I'd like to make sure I replicate your environment. |
Not sure what you are asking, but I am using simple dashboard view with Test Statistics Chart and Test Trend Chart However it is important to note that Test Trend Chart (seems to) show correctly the number of failing test. This is strange since I would expect that trend chart uses same data as pie chart but shows them over time. Hope this helps |
I am having the same problem with the Test Statistics Grid. The numbers for one job have never populated and the others seem to not update. |
Neven, Definitely agree that it looks like something is wonky. Can you throw the "Test Statistics Grid" up on your dashboard, and show me the result of that? It shows all the individual jobs being tallied up, and that might help diagnose the issue. I don't see anywhere in the code where there should be an issue specific to never-passed jobs, so I'd like to try and get more data. UPDATE: I went through your latest screenshot, and it doesn't look like the "successful" tests for those two jobs are being included in the chart either. Is there anything special about those jobs? What plugin is publishing those test results? |
Curtis, Regarding the Grid, what type of tests are being published? I fixed an issue with the TAP plugin where it wasn't publishing its results in a way that the grid liked. I'd recommend opening a separate defect report for that one, tied to whatever test tool is trying to publish results. You can reference https://issues.jenkins-ci.org/browse/JENKINS-22016 which was the fix for the TAP plugin. |
I'm seeing the same problem. I think it stems from the fact that TestUtil.summarizeJob() calls job.getAction(TestResultProjectAction.class) In my debugging, job.getAction() leads to the following calls: job.getAllActions() - Actionable.createFor() - SimpleBuildStep.LastBuildActionFactory.createFor() Inside LastBuildActionFactory.createFor(), you can see that project actions will only be added to the collection returned if getLastSuccessfulBuild() is not null. Because of this, the dashboard's calls to job.getAction(TestResultProjectAction.class) return null and a blank test result is added to the summary. My hunch is that in general, only showing information from the last successful build isn't what people are looking for. In my case, I always want to see information from the last build that produced a test result, even if that build failed. You might be able to borrow from here, and call it here, instead of job.getAction(TestResultProjectAction.class). |
Hi, I'm also facing the same issue. Do we have any update on this? "Test Statistics Grid" showing '0' for failed test cases.
Regards, Neel |
Good day, guys!
Jenkins ver - 2.150.1 Plugin ver - 2.10 |
any update on this issue? |
Hi,
There is a problem in the latest release:
If you have job that history is kept let say for 14 days and it was never been green the "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests
PS: here is a screenshot with calculations to confirm the bug - http://screencast.com/t/1QkzO8Ggy - the stats are completely wrong
Originally reported by ndinev, imported from: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
The text was updated successfully, but these errors were encountered: