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

Occasional unlogged "ERROR: Expected to het an id but got instead on 'hg log --rev . --template {node} command." failure on an houly job

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: mercurial-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.379 / Mercurial plugin version 1.33
    • Similar Issues:

      Description

      I have a job that's kicked off hourly. On 5 of the last 24 runs, I've seen the failure below. This looks a lot like JENKINS-7111, but I'm not using the Timestamper plugin mentioned in that ticket.

      This has just started happening in the past day or so, after upgrading to 1.379. Prior to that I was running either 1.374 or 1.375.

      The project involved is currently pretty quiet commit-wise, espeically over the last couple days, so the 'hg log --rev' command value should be giving the same results for recent runs.

      I also see that these failures are not being logged in the hudson.log file.

      The console output is below.

      ==================================================================================

      Started by timer
      Building remotely on buildslave.fake
      [fake-job] $ hg incoming --quiet --bundle hg.bundle --template "<changeset node='

      {node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev trunk
      [fake-job] $ hg log --rev . --template {node}

      ERROR: Expected to get an id but got instead.
      Sending e-mails to: me@buildslave.fake
      Finished: FAILURE

        Attachments

          Activity

          Hide
          jpabloae jpabloae added a comment - - edited

          jglick,

          After a week we haven't faced this issue any more. We previously used to have it at least once a day. So the fixes appears to be working very well, thank you!

          Show
          jpabloae jpabloae added a comment - - edited jglick, After a week we haven't faced this issue any more. We previously used to have it at least once a day. So the fixes appears to be working very well, thank you!
          Hide
          jglick Jesse Glick added a comment -

          I've tried to release 1.35 using new site infrastructure. So far so good; we'll see if it actually appears on the update center.

          Show
          jglick Jesse Glick added a comment - I've tried to release 1.35 using new site infrastructure. So far so good; we'll see if it actually appears on the update center.
          Hide
          g7r g7r added a comment -

          It seems that problem is fixed in trunk version of plugin.

          Show
          g7r g7r added a comment - It seems that problem is fixed in trunk version of plugin.
          Hide
          jglick Jesse Glick added a comment -

          No planned release date yet.

          As mentioned in commit log, I have no real way of knowing that the change improved matters. If you are seeing the issue frequently, you are a valuable tester. Please consider building your own copy of 1.35-SNAPSHOT and running it on your server. (I can also supply you with a mercurial.hpi if you are not comfortable building from source.)

          Show
          jglick Jesse Glick added a comment - No planned release date yet. As mentioned in commit log, I have no real way of knowing that the change improved matters. If you are seeing the issue frequently, you are a valuable tester. Please consider building your own copy of 1.35-SNAPSHOT and running it on your server. (I can also supply you with a mercurial.hpi if you are not comfortable building from source.)
          Hide
          jpabloae jpabloae added a comment -

          Thank you for the fix, this issue happens very frequently in our instances. Do you have any planned dates for the 1.35 release of the plugin?

          Show
          jpabloae jpabloae added a comment - Thank you for the fix, this issue happens very frequently in our instances. Do you have any planned dates for the 1.35 release of the plugin?

            People

            • Assignee:
              jglick Jesse Glick
              Reporter:
              pwan pwan
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: