Can you share the output of: svn log -r 12192 -l 1 --xml
The less sanitized the better, although I guess line 3 will be the most critical. I suspect some sort of encoding issue, but I don't know why this is system dependent. Perhaps something to do with locales? On Tuesday, April 7, 2015 at 2:18:43 PM UTC-4, Richard Parks wrote: > > Hi, we're running two separate linux clusters, both with different > versions of rbt, svn, python and linux but both show the same post error: > > CRITICAL: not well-formed (invalid token): line 3, column 28 > > This error comes up on any rbt diff or post, and is not a problem with the > svn repo as I can diff and post fine locally. > > The first cluster: > >>> RBTools 0.7.2 > >>> Python 2.7.7 (default, Feb 10 2015, 10:28:27) > [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] > >>> Running on Linux-2.6.18-164.15.1.el5-x86_64-with-redhat-5.4-Final > Subversion command-line client, version 1.7.5. > > > The second cluster: > >>> RBTools 0.7.1 > >>> Python 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) > [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] > >>> Running on Linux-2.6.32-431.29.2.el6.x86_64-x86_64-with-centos-6.5- > Final > Subversion command-line client, version 1.7.16. > > > > running diff in debug: > rbt diff --debug 12192 12208 > >>> RBTools 0.7.2 > >>> Python 2.7.7 (default, Feb 10 2015, 10:28:27) > [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)] > >>> Running on Linux-2.6.18-164.15.1.el5-x86_64-with-redhat-5.4-Final > >>> Home = /home/myusername > >>> Current directory = /projects/fw/myusername/myprojectbranch > >>> Checking for a Subversion repository... > >>> Running: svn info --non-interactive > >>> Running: diff --version > >>> Running: svn --version -q > >>> repository info: Path: http://mycompanysvnrepo, Base path: > /branches/development/myprojectbranch, Supports changesets: False > >>> Making HTTP GET request to http://reviewboard.mycompany > >>> Running: svn log -r 12192 -l 1 --xml > Password for 'myusername': > Traceback (most recent call last): > File "/usr/local/bin/rbt", line 8, in <module> > load_entry_point('RBTools==0.7.2', 'console_scripts', 'rbt')() > File > "/usr/local/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/main.py" > , line 133, in main > command.run_from_argv([RB_MAIN, command_name] + args) > File > "/usr/local/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/__init__.py" > , line 555, in run_from_argv > exit_code = self.main(*args) or 0 > File > "/usr/local/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/commands/diff.py" > , line 47, in main > revisions = tool.parse_revision_spec(args) > File > "/usr/local/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/clients/svn.py" > , line 166, in parse_revision_spec > 'base': self._convert_symbolic_revision(revisions[0]), > File > "/usr/local/lib/python2.7/site-packages/RBTools-0.7.2-py2.7.egg/rbtools/clients/svn.py" > , line 183, in _convert_symbolic_revision > root = ElementTree.fromstring(log) > File "/usr/local/lib/python2.7/xml/etree/ElementTree.py", line 1300, in > XML > parser.feed(text) > File "/usr/local/lib/python2.7/xml/etree/ElementTree.py", line 1642, in > feed > self._raiseerror(v) > File "/usr/local/lib/python2.7/xml/etree/ElementTree.py", line 1506, in > _raiseerror > raise err > xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 3, > column 28 > > To me this looks like a python error but both clusters show exactly the > same error and are running different version of python. Incidentally when I > post locally and it works, I'm running python 2.7.9. > > Has anyone else encountered this error? Any help greatly appreciated! > Thanks in advance. > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
