On 1/5/2016 5:29 PM, Joe Mistachkin wrote:
Ross Berteig wrote:
I figure the first step to building test cases for JSON support is to
prove I can build a fossil that passes its existing tests. Apparently
that isn't the case.
Please try setting the TEMP environment variable to a directory writable
by the current user.
Aha. I knew it must be something simple and obvious that was not set
right that I wasn't seeing.
Would it make sense to add a 000_FIRST.test (named something that
guarantees it to run first) that verifies easy to miss assumptions made
by the test suite itself, such as $TEMP is writeable?
The tests on tag release now finish without halting, but not without
failures.
Now the next obvious question is if it says "65 errors out of 27300
tests", what else am I missing?
***** Final result: 65 errors out of 27300 tests
***** Failures: clean-6 clean-12 clean-18 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 mv-soft-relative-2 mv-soft-relative-4 mv-hard-relative-2
mv-hard-relative-4 mv-soft-absolute-2 mv-soft-absolute-4
mv-hard-absolute-2 mv-hard-absolute-4 rm-soft-relative-4
rm-soft-relative-6 rm-hard-relative-4 rm-hard-relative-6
rm-soft-absolute-4 rm-soft-absolute-6 rm-hard-absolute-4
rm-hard-absolute-6 revert-1-1 revert-1-2 revert-1-3 revert-1-4
revert-1-5 revert-1-6 revert-1-7 revert-2-1 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
Those sound like I ought to be concerned....
For future reference, is there an official way to get a log of the
failures, perhaps with more information about what was wrong? I'm sure I
can just write stdout and stderr to a file, but if there are useful
options and settings for the test runner it would be nice to know about
them.
--
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
