Gopublic

Bug Reports

Use this forum to report problems you are having with Go and to seek resolution with fellow community members

This is a public Discussion Area  publicRSS

Post

    mmgn.com
    Modification check failed for pipeline: Unable to parse svn...
    Post posted February 20, 2010 by mmgn.com
    1396 Views, 3 Comment
    Topic:
    Modification check failed for pipeline: Unable to parse svn log output:
    Body:

    Could someone help me with this? Thanks in advance!

    2010-02-20 14:40:22,066 INFO [MessageListener for MaterialCheckListener] BuildCauseProducerService:136 - Modification check failed for pipeline: MMGN.com
    java.lang.RuntimeException: Unable to parse svn log output: <?xml version="1.0"?>
    <log>
    <logentry
    revision="3861">
    </logentry>
    </log>
    at com.thoughtworks.cruise.util.ExceptionUtils.bomb(ExceptionUtils.java:20)
    at com.thoughtworks.cruise.domain.materials.svn.SvnCommand.latestModification(SvnCommand.java:83)
    at com.thoughtworks.cruise.domain.materials.svn.SvnMaterial.latestModification(SvnMaterial.java:58)
    at com.thoughtworks.cruise.domain.MaterialRevisions.addLatestRevisionFrom(MaterialRevisions.java:39)
    at com.thoughtworks.cruise.server.scheduling.BuildCauseProducerService.latestRevisions(BuildCauseProducerService.java:163)
    at com.thoughtworks.cruise.server.scheduling.BuildCauseProducerService.produceBuildCause(BuildCauseProducerService.java:109)
    at com.thoughtworks.cruise.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:68)
    at com.thoughtworks.cruise.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:77)
    at com.thoughtworks.cruise.server.messaging.MaterialCheckListener.onMessage(MaterialCheckListener.java:20)
    at com.thoughtworks.cruise.server.messaging.MaterialCheckListener.onMessage(MaterialCheckListener.java:6)
    at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.onMessage(JMSMessageListenerAdapter.java:32)
    at com.thoughtworks.cruise.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:49)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.RuntimeException: Unable to parse svn log output: <?xml version="1.0"?>
    <log>
    <logentry
    revision="3861">
    </logentry>
    </log>
    at com.thoughtworks.cruise.util.ExceptionUtils.bomb(ExceptionUtils.java:24)
    at com.thoughtworks.cruise.util.SvnLogXmlParser.parse(SvnLogXmlParser.java:29)
    at com.thoughtworks.cruise.domain.materials.svn.SvnCommand.parseSvnLog(SvnCommand.java:104)
    at com.thoughtworks.cruise.domain.materials.svn.SvnCommand.latestModification(SvnCommand.java:80)
    ... 11 more
    Caused by: java.lang.NullPointerException
    at com.thoughtworks.cruise.util.SvnLogXmlParser.convertDate(SvnLogXmlParser.java:82)
    at com.thoughtworks.cruise.util.SvnLogXmlParser.parseLogEntry(SvnLogXmlParser.java:48)
    at com.thoughtworks.cruise.util.SvnLogXmlParser.parseDOMTree(SvnLogXmlParser.java:41)
    at com.thoughtworks.cruise.util.SvnLogXmlParser.parse(SvnLogXmlParser.java:27)
    ... 13 more

    Comment

    • Yogi Kulkarni
      posted February 23, 2010 by Yogi Kulkarni

      Hi,

      Could you give us more details about:

      - Cruise Server version

      - Subversion version

      - Operating System

      Thanks,

      Yogi

    • mmgn.com
      posted February 23, 2010 by mmgn.com

      Hi

      Cruise Server Version: 1.3.2(8704-77864ef38eda)
      JVM version: 10.0-b23
      OS Information: Windows Server 2008 6.0

      Subversion command-line client, version 1.6.6.

      I have three pipelines, the other two works, this one does not work for some reason.

      Other's have suggested this: http://community.thoughtworks.com/posts/8b51df5c3a

      The XML is not in another locale, we don't have any other locale installed.

      Thanks for your help.

    • fkurzawa
      posted December 19, 2011 by fkurzawa

      I just started getting the same error on a pipeline that has been working just fine up until now. No changes to the pipeline.

      Go Server version 2.3.1

      Running on Linux Red Hat 4.1.2-50

      SVN version 1.4.6

       

      Thanks in advance,

      Frank