Add a new XFail test for a wc corruption race condition (which I believe was introduced in r23342) which is easy to trigger if interactive conflict resolution dies in the middle of prompting. Specifically, we run an update with interactive-conflicts on but close stdin immediately, so the prompt errors out; then the dir_baton pool cleanup handlers in the WC update editor flush and run incomplete logs and lead to WC corruption, detectable by another update command.
Add a new XFail test for a wc corruption race condition (which I
believe was introduced in r23342) which is easy to trigger if
interactive conflict resolution dies in the middle of prompting.
Specifically, we run an update with interactive-conflicts on but close
stdin immediately, so the prompt errors out; then the dir_baton pool
cleanup handlers in the WC update editor flush and run incomplete logs
and lead to WC corruption, detectable by another update command.

(It's possible that the exact "expected" values are incorrect, but at
the very least this test shouldn't lead to a checksum mismatch!)

* subversion/tests/cmdline/update_tests/py
  (eof_in_interactive_conflict_resolver): New XFail test.

jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion,jmckaskill/subversion