Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37600

Dashboard View Test Statistics Grid showing only zeros for Robot Framework tests

      We have a project where we run Robot Framework tests and in Test Statistics Grid we are seeing only zeros, while on Test Trend Chart of the same project we are seeing right (non-zero) data.

      See more details in the attached screen shot.

          [JENKINS-37600] Dashboard View Test Statistics Grid showing only zeros for Robot Framework tests

          Taras Kurdyna added a comment -

          In Jenkins logs all I am seeing:

          Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration
          Couldn't parse duration for suite Gemini E2E
          Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration
          Couldn't parse duration for suite E2E
          Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration
          Couldn't parse duration for suite Testsuites

          Taras Kurdyna added a comment - In Jenkins logs all I am seeing: Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration Couldn't parse duration for suite Gemini E2E Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration Couldn't parse duration for suite E2E Aug 22, 2016 4:25:47 PM WARNING hudson.plugins.robot.model.RobotSuiteResult getDuration Couldn't parse duration for suite Testsuites

          Is this on anyone's radar to look at?  This is a big problem for us where we cannot report our Robot results in the dashboard.

          It feels like this is an issue on the Robot Framework Plugin side as perhaps the test results are not conforming to some interface that the dashboard is expecting...

          Christopher Shannon added a comment - Is this on anyone's radar to look at?  This is a big problem for us where we cannot report our Robot results in the dashboard. It feels like this is an issue on the Robot Framework Plugin side as perhaps the test results are not conforming to some interface that the dashboard is expecting...

          Alex Radinsky added a comment -

          Did you figured out how to fix the "Couldn't parse duration for suite" ?

          I'm getting tons of those warning in my system and I think it keeps the cpu very high.

          Alex Radinsky added a comment - Did you figured out how to fix the "Couldn't parse duration for suite" ? I'm getting tons of those warning in my system and I think it keeps the cpu very high.

          We also have (tons) these warnings in our jenkins log.

          Tapio Reijonen added a comment - We also have (tons) these warnings in our jenkins log.

          Tatu Kairi added a comment -

          We in the maintenance team have never even heard of Dashboard View before these issues got reported. Thanks for bringing the issue up!

          Since Dashboard View is separate plugin (ie. not default Jenkins behaviour), we most certainly do not support whatever it expects. Therefore we need the capability first to begin with, which is covered in JENKINS-22603.

           

          Thus, as we do not have anything to fix, I'm closing this issue. Please follow the JENKINS-22603 ticket for when we can support Dashboard VIew to begin with. 

          Tatu Kairi added a comment - We in the maintenance team have never even heard of Dashboard View before these issues got reported. Thanks for bringing the issue up! Since Dashboard View is separate plugin (ie. not default Jenkins behaviour), we most certainly do not support whatever it expects. Therefore we need the capability first to begin with, which is covered in  JENKINS-22603 .   Thus, as we do not have anything to fix, I'm closing this issue. Please follow the  JENKINS-22603 ticket for when we can support Dashboard VIew to begin with. 

            vandyev Evan Van Dyke
            tkurdyna Taras Kurdyna
            Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: