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

test history does not scale for many builds, brings down hudson

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • junit-plugin
    • None
    • Platform: All, OS: All

      When clicking the test history at any level for a job with say 3,000 builds, the
      history table will load a few hundred rows and then hang, and the graph will
      never load. After a minute or two the hudson instance will be completely
      unresponsive or give Out Of Memory errors. Hudson will not even respond to a
      SIGTERM, I must do a SIGKILL to stop it.

      So in other words, the test history feature doesn't seem to work in projects
      where it would matter the most, and can be quite disruptive as it will bring
      down Hudson and all its jobs

          [JENKINS-4621] test history does not scale for many builds, brings down hudson

          mcrooney added a comment -

          Just to clarify, an example of a link in question is
          http://HUDSON/job/NAME/lastBuild/testReport/history

          mcrooney added a comment - Just to clarify, an example of a link in question is http://HUDSON/job/NAME/lastBuild/testReport/history

          mcrooney added a comment -

          FYI this is still confirmed on Hudson 1.354; Hudson has eaten 2.5GB of memory so far since I clicked the History button and is using 100% CPU. Any thoughts?

          mcrooney added a comment - FYI this is still confirmed on Hudson 1.354; Hudson has eaten 2.5GB of memory so far since I clicked the History button and is using 100% CPU. Any thoughts?

          Kohsuke Kawaguchi added a comment - Fixed in 1.388 as https://github.com/hudson/hudson/commit/39cb6f709d6ae9beab59fd875da0c4ad6a5920a2

          mcrooney added a comment -

          Thanks!!!!!

          mcrooney added a comment - Thanks!!!!!

            Unassigned Unassigned
            mcrooney mcrooney
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: