subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Martin <phi...@codematters.co.uk>
Subject Blame behaviour change in 1.9
Date Tue, 09 Jun 2015 16:50:10 GMT
Build 1.8 and 1.9 (I'm building 1684452).  Run a 1.9 server pointing at
the 1.8 build directory; the server can be httpd or svnserve, but
svnserve is probably easiest:

  ../obj-1.9/subversion/svnserve/svnserve -Tdr ../obj-1.8/subversion/tests/cmdline

then run blame_tests.py 10:

  cd ../obj-1.8/subversion/tests/cmdline
  .../blame_tests.py 10 --url svn://localhost

and the test fails.  We can see the cause by running blame on the
working copy of the failed test with the 1.9 server.  The 1.8 client
gives the wrong output:

$ ../../svn/svn blame -g svn-test-work/working_copies/blame_tests-10/trunk/iota
       2    jrandom This is the file 'iota'.
       2    jrandom 'A' has changed a bit, with 'upsilon', and 'xi'.

while the 1.9 client gives the correct output:

$ svn blame -g svn-test-work/working_copies/blame_tests-10/trunk/iota
       2    jrandom This is the file 'iota'.
G     11    jrandom 'A' has changed a bit, with 'upsilon', and 'xi'.

If I kill the 1.9 server and start a 1.8 server then both clients gives
the correct output.  It appears the 1.9 server is sending data that the
1.8 client does not interpret correctly.

-- 
Philip

Mime
View raw message