File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -8,15 +8,14 @@ set -o nounset
88# mounted rather than built in, since it could only be taken with a server up.
99# Both are said at once, with the indexer first, so the answer reads as one
1010# group after another
11- RESULTS=" $( mktemp -d) "
12- clean () { rm -rf " $RESULTS " ; }
13- trap clean EXIT
11+ set -- /benchmark.json
1412
15- cp /benchmark.json " $RESULTS /index.json"
13+ for RESULT in /results/* .json
14+ do
15+ if [ -f " $RESULT " ]
16+ then
17+ set -- " $@ " " $RESULT "
18+ fi
19+ done
1620
17- if [ -d /results ]
18- then
19- find /results -maxdepth 1 -name ' *.json' -exec cp {} " $RESULTS /" \;
20- fi
21-
22- jq --slurp ' add' " $RESULTS " /* .json
21+ jq --slurp ' add' " $@ "
Original file line number Diff line number Diff line change @@ -39,9 +39,9 @@ test-hurl:
3939
4040# A suite that carries a script saying what it wants measured is measured
4141# before its tests run, so what is timed is an instance warmed deliberately
42- # rather than one that has just served a whole test suite. A run that stops
43- # part way through leaves nothing behind, as a partial answer that reads like a
44- # complete one is worse than no answer at all
42+ # rather than one that has just served a whole test suite. What a run writes is
43+ # named apart until it is complete, so a run that stops part way through cannot
44+ # leave behind a partial answer that reads like a whole one
4545.PHONY : test-benchmark
4646test-benchmark :
4747ifneq ($(wildcard benchmark.py) ,)
You can’t perform that action at this time.
0 commit comments