Cannot checkout or clean up using 1.9 dev build

I recently tried the nightly build from TortoiseSVN, with the following
version information for the supplied command-line tools:

svn, version 1.9.0-dev (under development)
   compiled Apr 27 2015, 03:09:52 on x86-microsoft-windows

Copyright (C) 2015 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
  - with Cyrus SASL authentication
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
  - using serf 1.3.8
  - handles 'http' scheme
  - handles 'https' scheme

The following authentication credential caches are available:

* Wincrypt cache in C:\Users\(my username)\AppData\Roaming\Subversion

I get the following error when I try to check out a working copy from my
repository at work (exact path names obfuscated but length unchanged, in
case it matters), leaving a partially downloaded working copy:

svn: E155009: Failed to run the WC DB work queue associated with
'C:\Project_Files\Proj_Dev\Prog_svn_1.9_cmdline', work item 2160
(file-install 234
Logical_Architecture/APP/App_PL_Verification/XXX/XXX_XXXs/XXX_7_APPDB_PROJ_PROG-0000-0021_BE/APPDB_PROJ_PROG-0000-0021.SUP/APPDB_PROJ_PROG-0000-0021/APPDB_PROJ_PROG-0000-0021/APPDB_PROJ_PROG-0000-0021.SUP/XXX_APPDB_PROJ_PROG-0000-002101.CRC
1 0 1 1)
svn: E720123: The filename, directory name, or volume label syntax is
incorrect.

I get the same error message when I try "svn cleanup" in this partial
working copy.

In case it's not clear, I get this error when running the command-line
tools (in addition to the TortoiseSVN GUI), so I know it's not something
introduced by the TortoiseSVN folks.

Is there more detail I can gather to help resolve this, or should I just
sit and wait and hope it gets fixed before 1.9 gets released?
Received on 2015-04-27 18:06:51 CEST