Thus said Ross Berteig on Thu, 07 Jan 2016 23:55:12 -0800: > Exactly. And I think it is a good idea for the test suite to run from > a folder outside of all checkouts for a lot of reasons.
Perhaps we should update the test: make target to create a temporary directory, cd to it and run tests from there... > Does that work for you (anyone?) right now from trunk? Depends on what you mean by ``work'' I suppose, but it does for me. There are some failures: ***** Final result: 38 errors out of 27800 tests ***** Failures: relative-tree-name-100.1 relative-tree-name-100.2 relative-tree-name-100.3 relative-tree-name-100.4 relative-tree-name-101.1 relative-tree-name-101.2 relative-tree-name-101.3 relative-tree-name-102.1 relative-tree-name-102.2 relative-tree-name-102.3 relative-tree-name-103.1 absolute-tree-name-100.1 absolute-tree-name-100.2 absolute-tree-name-100.3 absolute-tree-name-100.4 absolute-tree-name-101.1 absolute-tree-name-101.2 absolute-tree-name-101.3 absolute-tree-name-102.1 absolute-tree-name-102.2 absolute-tree-name-102.3 absolute-tree-name-103.1 merge-utf-27-23 merge-utf-27-32 merge_multi-4 merge_renames-5 th1-checkout-1 th1-checkout-2 th1-header-2 th1-footer-2 th1-footer-3 th1-artifact-3 th1-artifact-5 th1-artifact-7 th1-artifact-9 th1-globalState-1 th1-globalState-8 th1-encode64-3 > And that fails for me because a passel of cases in file1.test and > th1.test appear to require an open checkout, but don't provide one by > calling repo_init. If they require repo_init and aren't calling it, then I guess they need to be updated. Andy -- TAI64 timestamp: 40000000569020ea _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
