On 1/20/2016 4:12 AM, Baruch Burstein wrote:
Can https://www.fossil-scm.org/index.html/info/3baa7e3dc195a888 be closed? I would assume so, but am not at all familiar with the TH1/test areas of the code and so would rather not do it on my own.
The version of th1.test on trunk (at least as of [0d757274d3]) does not have the code inserted by that branch. However, it instead compares the result of "fossil test-th-eval --open-config "setting autosync" against a list of values, namely "0", "1", and "on" rather than just "1".
I don't spot any test cases in th1.test that depend on the effect of the autosync setting, so that difference likely covers the issue addressed in that branch.
The handful of test cases in th1.test that depended on running within a checkout of the fossil repository have been fixed to do so safely.
If a clean and empty repo were needed for the others, the repo_init command is available for use, it does exactly what the edit on this branch does, namely create an empty repository for use by subsequent test cases.
As it stands, th1.test passes all tests with fossil built from a simple configuration on Windows, and from both simple and full-featured configurations on Ubuntu.
It looks to me like the branch can be closed. -- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
