On 14 May 2018 at 18:23, Chris Lambertus <[email protected]> wrote: > > >> On May 14, 2018, at 9:59 AM, Chris Lambertus <[email protected]> wrote: >> >> >> >>> On May 14, 2018, at 9:39 AM, sebb <[email protected]> wrote: >>> >>> As the subject says. >>> >>> The recent master restart has not helped. >> >> >> buildmaster@buildbot-vm:~/master1$ buildbot checkconfig . >> Config file is good! > > > It looks like the configscanner still isn’t working properly. > > buildmaster@buildbot-vm:~/master1/projects$ svn status -u > * 1029710 _template.conf > * 1029710 openjpa.conf > * 1029710 attic-site.conf > * 1029710 attic-jekyll.conf > * 1029710 jmeter.conf > > Here’s the error from the logfile after configscanner was restarted: > > [2018-05-14 17:18:08,803]: Bad JSON or something: Command '['/usr/bin/svn', > 'info', '--show-item', 'last-changed-revision', 'projects']' returned > non-zero exit status 1
That was one of the new commands used in the new version of the scanner... > Running that command locally throws an error because the subversion client is > too old (1.8.8.) There is a problem with apt on that machine and it’s unable > to upgrade svn, so I’ll need to look into it further. If it proves difficult to update subversion, the scanner could be updated to use a different way of obtaining the last-changed-revision. > I have manually updated and run reconfigure, so the changes should be > apparent now. Thanks. > -Chris >
