• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • Linux, JDK 6. 1.349 w/ Mercurial plugin 1.25.

      I upgraded two Hudson servers, both using latest Mercurial plugin, to Hudson 1.349. One seems fine. On the other one, SCM polling is completely broken (for jobs built either on master or slaves):

      Last Mercurial Polling Log

      Started on Mar 8, 2010 5:31:08 PM
      ERROR: Failed to record SCM polling
      [8mha:AAA....<junk>....AAA==[0mjava.lang.AbstractMethodError
      at hudson.scm.SCM.poll(SCM.java:344)
      at hudson.model.AbstractProject.poll(AbstractProject.java:1149)
      at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:319)
      at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:348)
      at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)

      The stack trace is odd because it looks like it is throwing AME from inside the catch block for AME, calling the older method!

          [JENKINS-5866] AbstractMethodError from SCM.poll

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-2180 [ JENKINS-2180 ]
          Andrew Bayer made changes -
          Link New: This issue duplicates JENKINS-5756 [ JENKINS-5756 ]
          Jesse Glick made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jesse Glick made changes -
          Resolution Original: Cannot Reproduce [ 5 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Jesse Glick made changes -
          Description Original: I upgraded two Hudson servers, both using latest Mercurial plugin, to Hudson 1.349. One seems fine. On the other one, SCM polling is completely broken (for jobs built either on master or slaves):

          Last Mercurial Polling Log

          Started on Mar 8, 2010 5:31:08 PM
          ERROR: Failed to record SCM polling
          [8mha:AAAAVx+LCAAAAAAAAABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0m1W6NqK7pC2JmJgaGiiEEKTYMzhAYpZIAARpDCAgBF2FTYYAAAAA==[0mjava.lang.AbstractMethodError
          at hudson.scm.SCM.poll(SCM.java:344)
          at hudson.model.AbstractProject.poll(AbstractProject.java:1149)
          at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:319)
          at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:348)
          at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
          at java.util.concurrent.FutureTask.run(FutureTask.java:138)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)

          The stack trace is odd because it looks like it is throwing AME from inside the catch block for AME, calling the older method!
          New: I upgraded two Hudson servers, both using latest Mercurial plugin, to Hudson 1.349. One seems fine. On the other one, SCM polling is completely broken (for jobs built either on master or slaves):

          Last Mercurial Polling Log

          Started on Mar 8, 2010 5:31:08 PM
          ERROR: Failed to record SCM polling
          [8mha:AAA....<junk>....AAA==[0mjava.lang.AbstractMethodError
          at hudson.scm.SCM.poll(SCM.java:344)
          at hudson.model.AbstractProject.poll(AbstractProject.java:1149)
          at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:319)
          at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:348)
          at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
          at java.util.concurrent.FutureTask.run(FutureTask.java:138)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)

          The stack trace is odd because it looks like it is throwing AME from inside the catch block for AME, calling the older method!
          Andrew Bayer made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135958 ] New: JNJira + In-Review [ 203770 ]

            Unassigned Unassigned
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: