forked from opprop/ontology
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathtest-ontology.sh
executable file
·39 lines (32 loc) · 1.06 KB
/
test-ontology.sh
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
#!/bin/bash
# Failed the whole script if any command failed
set -e
# Running Ontology test suite
gradle test
WORKING_DIR=$(pwd)
if [ -z "${JSR308}" ] ; then
export JSR308=$(cd $(dirname "$0")/.. && pwd)
fi
# Pulling DLJC, if there is no DLJC.
# This is specially for adding ontology as
# a travis downstream test for CFI.
# Because CFI doesn't pull DLJC, but ontology
# needs DLJC to run the benchmark test.
#
# TODO: I don't think this is the best place
# to place this logic of pulling DLJC, as
# it actually makes this testing script
# aware of travis. However, create a seperate
# script for only pulling DLJC also seems
# an overkill. Maybe seperate below logic
# in the future if we need to do more things
# specially for travis downstream test.
SLUGOWNER=${TRAVIS_REPO_SLUG%/*}
if [[ "$SLUGOWNER" == "" ]]; then
SLUGOWNER=opprop
fi
if [ ! -d ../do-like-javac ] ; then
(cd $JSR308 && git clone https://github.com/${SLUGOWNER}/do-like-javac.git)
fi
# Running Ontology on working benchmarks
python run-ontology-on-corpus.py --corpus-file worked-benchmarks.yml