when travis is throttling resourcse more than usual (resources are
dynamically allocated since we are not using a paid service), it
can be the case that tests fail even more than usual.
this number may need to be increased further if 5 does not provide enough
reliability
Differential Revision: https://phab.enlightenment.org/D6920
this is just spam that fills up the logs and sometimes causes builds to
abort when they reach the maximum log size
Differential Revision: https://phab.enlightenment.org/D6788
the tests have all been compiled at this point using the check-build
target (separately) in order to split out test compile failures from
runtime failures, so use the check-TESTS target to run the tests without
checking whether the tests are built first
Differential Revision: https://phab.enlightenment.org/D6619
this adds a script to run make check after the build has finished,
repeating tests 3 times to try and reduce false positives from intermittent
failure tests
ref T7094
Differential Revision: https://phab.enlightenment.org/D6617
Mike Blumenkrantz