summaryrefslogtreecommitdiff
path: root/shippable.yml
diff options
context:
space:
mode:
authorTyler Reddy <tyler.je.reddy@gmail.com>2020-06-16 15:07:07 -0600
committerTyler Reddy <tyler.je.reddy@gmail.com>2020-06-16 15:07:07 -0600
commitbdf6cefd176e9307efec83a0fa56cc0348091ca1 (patch)
tree6ab68b70c5ac725a464ac7f86490c1a31b7875f5 /shippable.yml
parentda1621637b7c59c155ec29466fb5f810ebd902ac (diff)
downloadnumpy-bdf6cefd176e9307efec83a0fa56cc0348091ca1.tar.gz
MAINT, CI: disable Shippable cache
* a quick look at the NumPy CI failures on Shippable service clearly shows the full test suite passing and a negative exit code only because of the failed cache restore * since the jobs are running in about 20 minutes even without the use of a cache, just try turning if off
Diffstat (limited to 'shippable.yml')
-rw-r--r--shippable.yml10
1 files changed, 1 insertions, 9 deletions
diff --git a/shippable.yml b/shippable.yml
index dc3617e12..547668d5c 100644
--- a/shippable.yml
+++ b/shippable.yml
@@ -53,15 +53,7 @@ build:
# run the test suite
- python runtests.py -n --debug-info --show-build-log -- -rsx --junit-xml=$SHIPPABLE_REPO_DIR/shippable/testresults/tests.xml -n 2 --durations=10
- cache: true
- cache_dir_list:
- # the NumPy project uses a single Amazon S3 cache
- # so upload the parent path of the Python-specific
- # version paths to avoid i.e., 3.6 overwriting
- # 3.7 pip cache (seems to be an issue)
- - /root/.cache/pip/wheels
-
-
+ cache: false
# disable email notification
# of CI job result