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

Load statistics medium shows wrong time period

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None
    • Jenkins 2.222.4
    • 2.342

    Description

      Load statistics chart for timespan "Medium" shows wrong time period or respectively is no more updated. 

      Charts for "Short" and "Long" are ok.
      Screenshots created Nov. 24th 2020, at 8:30. Graph for "medium timespan" shows period from 17:19 to 17:09, but I´m expecting 8:30 to 8:30.

      Medium:

      Short:

      Long:

       

      Attachments

        Activity

          danielbeck Daniel Beck added a comment -

          Strange that this graph has a discontinuity near 09:23 rather than 08:30.

          TZ? My local Jenkins is currently 2 hours off (latest label is "Sun 13:07" while it's 15:24), which corresponds to the (new) CEST offset from UTC.

          danielbeck Daniel Beck added a comment - Strange that this graph has a discontinuity near 09:23 rather than 08:30. TZ? My local Jenkins is currently 2 hours off (latest label is "Sun 13:07" while it's 15:24), which corresponds to the (new) CEST offset from UTC.

          Screenshots created Nov. 24th 2020, at 8:30. Graph for "medium timespan" shows period from 17:19 to 17:09, but I´m expecting 8:30 to 8:30.

          Medium:

          Strange that this graph has a discontinuity near 09:23 rather than 08:30.

          kon Kalle Niemitalo added a comment - Screenshots created Nov. 24th 2020, at 8:30 . Graph for "medium timespan" shows period from 17:19 to 17:09, but I´m expecting 8:30 to 8:30. Medium: Strange that this graph has a discontinuity near 09:23 rather than 08:30.

          At https://ci.jenkins.io/load-statistics?type=min, the graph looks OK, but it displays only one day worth of data rather than two. I think this is what happens when the Jenkins controller has been running for two days or longer. The graph breaks in a worse way only when Jenkins has been running for longer than one day, but less than two days.

          kon Kalle Niemitalo added a comment - At https://ci.jenkins.io/load-statistics?type=min , the graph looks OK, but it displays only one day worth of data rather than two. I think this is what happens when the Jenkins controller has been running for two days or longer. The graph breaks in a worse way only when Jenkins has been running for longer than one day, but less than two days.
          danielbeck Daniel Beck added a comment -

          Fix attempt in https://github.com/jenkinsci/jenkins/pull/6402

          While I have not seen the original reported behavior, the data does not extend past 1 day at the moment even in a "good" situation; so the PR should at a minimum address that, if the hypothesis by kon is correct.

          danielbeck Daniel Beck added a comment - Fix attempt in https://github.com/jenkinsci/jenkins/pull/6402 While I have not seen the original reported behavior, the data does not extend past 1 day at the moment even in a "good" situation; so the PR should at a minimum address that, if the hypothesis by kon is correct.
          kon Kalle Niemitalo added a comment - - edited

          No, dataLength was at most 1440 originally, and 1440 distinct column keys were generated; one per minute.

          Another possible fix might be to create custom objects as column keys. These would implement Comparable by comparing the underlying Date values, and override toString(). That way, the correctness would not depend on the date format.

          Or use the Date values as column keys and override AbstractCategoryItemLabelGenerator.generateColumnLabel, but that might require larger changes in Jenkins.

          kon Kalle Niemitalo added a comment - - edited No, dataLength was at most 1440 originally, and 1440 distinct column keys were generated; one per minute. Another possible fix might be to create custom objects as column keys. These would implement Comparable by comparing the underlying Date values, and override toString(). That way, the correctness would not depend on the date format. Or use the Date values as column keys and override AbstractCategoryItemLabelGenerator.generateColumnLabel , but that might require larger changes in Jenkins.

          People

            danielbeck Daniel Beck
            hjhafner Hans-Juergen Hafner
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: