Download:
parent 19:29f1205cdc33
20:fc0904a91aea default tip
Anton Shestakov <engored@ya.ru>, Sat, 29 Nov 2014 13:29:52 +0800
find-closest: something about ok and fail

1 files changed, 5 insertions(+), 2 deletions(-) [+]
find-closest/README.md file | annotate | diff | comparison | revisions
--- a/find-closest/README.md Sat Nov 29 13:27:09 2014 +0800
+++ b/find-closest/README.md Sat Nov 29 13:29:52 2014 +0800
@@ -39,11 +39,14 @@
`hgroot_3.sh`
- results are in seconds x 100, that is, 0.292 is how many a hundred calls to
the command takes, so each call is ~2.92ms
+- `ok` means the command ran correctly
First the test script runs (100 times for a good measure) all contestant
implementations in directories without a `.hg/` anywhere upwards (assuming your
`/` or `/tmp` is untracked), one directory deeper at a time: so the last result
is for the case when the script is 10 directories deep inside `/tmp/tmp.XXX/`
directory (test root). Then the test script adds an empty `.hg/` directory in
-the test root and runs everything one more time. There are quirks, as I said,
-but I believe the results are fairly accurate still.
+the test root and runs everything one more time. It also checks that the
+contestants produce the correct answer (path to the directory containing
+`.hg/`) and marks the time with either `ok` or `fail`. There are quirks, as I
+said, but I believe the results are fairly accurate still.