Den lör 7 okt. 2023 kl 06:52 skrev Yasuhito FUTATSUKI < futat...@yf.bsdclub.org>:
> Hi, > > On 2023/10/07 4:33, Daniel Sahlberg wrote: > > Den fre 6 okt. 2023 kl 19:34 skrev Nathan Hartman < > hartman.nat...@gmail.com > > >> The interesting thing, though, is that many tests in the test suite > >> compare expected error strings to actual error strings, involving > >> paths etc., and those are passing. > >> > >> What I also find interesting, besides the added escaping, is that the > >> expected path is very different than the actual path. Showing these > >> here without escaping for illustration: > >> > >> Expected: > >> > '/home/nathan/ramdrive/svndev/svn-trunk/subversion/tests/cmdline/svn-test-work/working_copies/copy_tests\-17' > >> Actual: > >> > '/home/nathan/ramdrive/svndev/ramdisk/svn-trunk/working_copies/copy_tests-17' > >> > >> The actual path is correct. > > In the copy_tests.wc_move_parent_into_child, it executes > 'svn mv . F/B', which specified paths as relative paths, > but its error message uses absolute real paths. > > On the other hand, expected paths are composed from > sbox.wc_dir which may contain symlinks, i.e. it may not > be real paths. > > If svn is called with relative paths, it can only see > cwd as a realpath, and absolute paths of argment paths > are composed from it. So the paths in error message we > can expect here is absolute real paths or relative paths > only (It assumes that relative paths passed from the > command line don't contain symlinks). > > I was able to reproduce the issue and thanks to Yasuhito's hints I was also able to fix it by using absolute paths when running the svn command. I've committed r1912826 with a simple fix which seems to work for me. Nathan, can you verify if it also works for you? Kind regards, Daniel Sahlberg
