• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 1.596 on Debian Wheezy, viewed with newest Chrome and Firefox

      Since the update to 1.596, the console output does not scroll down to follow the newest lines automatically. The page view stays at the top of the output, and one has to scroll down manually to watch the progress, which is tiresome.

          [JENKINS-26298] Console output does not scroll anymore

          sseidel added a comment -

          Sorry to hijack this bug, but after updating I have the same problem as Klemens. The output scrolls, but the build fails with the StackOverflowError. What exactly did you do to resolve the problem?

          sseidel added a comment - Sorry to hijack this bug, but after updating I have the same problem as Klemens. The output scrolls, but the build fails with the StackOverflowError. What exactly did you do to resolve the problem?

          Tom FENNELLY added a comment -

          @sseidel The stack overflow issue Klemens encountered had nothing to do with this fix.

          Tom FENNELLY added a comment - @sseidel The stack overflow issue Klemens encountered had nothing to do with this fix.

          Andreas Horst added a comment - - edited

          Well yes, since he states that configuring his Maven installations fixed it for him.

          However, I can confirm that jobs running fine in 1.597 fail in 1.598 with the same stack trace (StackOverflowError).

          @sseidel: try removing any "Deploy Maven Artifacts" post-build steps. This "fixed" the build for me.

          Apparently only the "Deploy Maven Artifacts" post-build step fails in 1.598. For example the Sonar post-build step runs fine. I think we should open a new report for this. For me this is a definite blocker.

          Edit: it's not the same stack trace:

          Maven RedeployPublisher use remote XXX maven settings from : /home/jenkins/.m2/settings.XXX.xml
          [INFO] Deployment in http://X.X.X/nexus/content/repositories/X-snapshots/ (id=X,uniqueVersion=true)
          Deploying the main artifact X-0.0.1-SNAPSHOT.jar
          FATAL: null
          java.lang.StackOverflowError
          	at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:606)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
          	at com.sun.proxy.$Proxy79.lookup(Unknown Source)
          	at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          	at java.lang.reflect.Method.invoke(Method.java:606)
          	at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40)
          	at com.sun.proxy.$Proxy79.lookup(Unknown Source)
          ...
          

          (note the recursion)

          Andreas Horst added a comment - - edited Well yes, since he states that configuring his Maven installations fixed it for him. However, I can confirm that jobs running fine in 1.597 fail in 1.598 with the same stack trace (StackOverflowError). @sseidel: try removing any "Deploy Maven Artifacts" post-build steps. This "fixed" the build for me. Apparently only the "Deploy Maven Artifacts" post-build step fails in 1.598. For example the Sonar post-build step runs fine. I think we should open a new report for this. For me this is a definite blocker. Edit: it's not the same stack trace: Maven RedeployPublisher use remote XXX maven settings from : /home/jenkins/.m2/settings.XXX.xml [INFO] Deployment in http://X.X.X/nexus/content/repositories/X-snapshots/ (id=X,uniqueVersion=true) Deploying the main artifact X-0.0.1-SNAPSHOT.jar FATAL: null java.lang.StackOverflowError at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy79.lookup(Unknown Source) ... (note the recursion)

          Daniel Beck added a comment -

          The fix for this issue was UI only (CSS/JavaScript), whatever server side issues there are, are unrelated. So please move this topic elsewhere – 20 people are watching and I doubt many of them care about the stack overflow.

          Before filing a bug about it, please note that it isn't a 'blocker' just because you rely on some feature that was broken. In most cases, these are Major ("major loss of functionality"), unless it impacts the overall operation of Jenkins.

          Daniel Beck added a comment - The fix for this issue was UI only (CSS/JavaScript), whatever server side issues there are, are unrelated. So please move this topic elsewhere – 20 people are watching and I doubt many of them care about the stack overflow. Before filing a bug about it, please note that it isn't a 'blocker' just because you rely on some feature that was broken. In most cases, these are Major ("major loss of functionality"), unless it impacts the overall operation of Jenkins.

          Andreas Horst added a comment -

          For those of the 20 people that DO care because they use Maven RedeployPublisher: Jenkins-26595

          Andreas Horst added a comment - For those of the 20 people that DO care because they use Maven RedeployPublisher: Jenkins-26595

          Ramakrishna P added a comment -

          Hi Guys,

          Sorry, for posting about this issue very late.
          Today we have upgraded our Jenkins instance from 1.558 to 1.599 and we started seeing lot of changes in the UI and configurations. After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot.

          After searching for the fix we got to know that it has been already addressed in the Ver. 1.598 itself. But still we are seeing this issue in the latest version 1.599.
          Can someone help us regarding this issue and let us know do we need to make any change in the configuration to fix the issue ?

          Thanks,
          Ramakrishna

          Ramakrishna P added a comment - Hi Guys, Sorry, for posting about this issue very late. Today we have upgraded our Jenkins instance from 1.558 to 1.599 and we started seeing lot of changes in the UI and configurations. After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot. After searching for the fix we got to know that it has been already addressed in the Ver. 1.598 itself. But still we are seeing this issue in the latest version 1.599. Can someone help us regarding this issue and let us know do we need to make any change in the configuration to fix the issue ? Thanks, Ramakrishna

          Daniel Beck added a comment -

          After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot.

          This issue is about the scrolling not working. The console still gets updated otherwise. If the console does not get updated, make sure you're not using the Bitnami Jenkins distribution (see JENKINS-25026), it's broken.

          Daniel Beck added a comment - After the upgrade we are started seeing this " Console Output Refresh " was not happening and it is troubling a lot. This issue is about the scrolling not working. The console still gets updated otherwise. If the console does not get updated, make sure you're not using the Bitnami Jenkins distribution (see JENKINS-25026 ), it's broken.

          Ramakrishna P added a comment -

          Please, find the attached JPG file for the version of Jenkins I am using.

          Ramakrishna P added a comment - Please, find the attached JPG file for the version of Jenkins I am using.

          Ramakrishna P added a comment -

          Hi Daniel,

          Thanks, for your quick reply.

          No, i am not using any special version ( Bitnami Jenkins ) / professional version of Jenkins. I am using the regular / OSS version of Jenkins in my test instance.

          Probably i may not be clear regarding the issue details. The issue is one I trigger my job and go n see the console output it is not showing the latest console output when the build is running.

          All it shows in " Spinning Icon " and it didn't get SCROLL THE LATEST LOG AT ALL. Once I refresh the page then it is loading the latest LOG.

          Thanks,
          Ramakrishna

          Ramakrishna P added a comment - Hi Daniel, Thanks, for your quick reply. No, i am not using any special version ( Bitnami Jenkins ) / professional version of Jenkins. I am using the regular / OSS version of Jenkins in my test instance. Probably i may not be clear regarding the issue details. The issue is one I trigger my job and go n see the console output it is not showing the latest console output when the build is running. All it shows in " Spinning Icon " and it didn't get SCROLL THE LATEST LOG AT ALL. Once I refresh the page then it is loading the latest LOG. Thanks, Ramakrishna

          Daniel Beck added a comment -

          Please file a new issue, the behavior you describe has nothing at all to do with this report.

          Daniel Beck added a comment - Please file a new issue, the behavior you describe has nothing at all to do with this report.

            tfennelly Tom FENNELLY
            lunifera Klemens Edler
            Votes:
            9 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: