aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar kwzrd <[email protected]>2020-11-13 08:30:27 +0100
committerGravatar kwzrd <[email protected]>2020-11-13 08:31:15 +0100
commit8885b15ca367398cd3208cbe3e9fce2e85b6a379 (patch)
tree390e2591233ed61a8b04cef37c2c19b60176a853
parentCI: invalidate environment cache (diff)
CI: disable 'continueOnError'
After #1219, we started to encounter issues with the cache being corrupted and CI failing due to 'pre-commit' not being installed after restore. Although it doesn't seem likely that this could have been the culprit, the issues began appearing shortly after merging the PR. Let's see what happens if we disable it.
-rw-r--r--azure-pipelines.yml2
1 files changed, 0 insertions, 2 deletions
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 0aa36a940..188ad7f93 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -37,7 +37,6 @@ jobs:
key: python | $(Agent.OS) | "$(python.pythonLocation)" | 2 | ./Pipfile | ./Pipfile.lock
cacheHitVar: PY_ENV_RESTORED
path: $(PYTHONUSERBASE)
- continueOnError: true
- script: echo '##vso[task.prependpath]$(PYTHONUSERBASE)/bin'
displayName: 'Prepend PATH'
@@ -65,7 +64,6 @@ jobs:
inputs:
key: pre-commit | "$(python.pythonLocation)" | 0 | .pre-commit-config.yaml
path: $(PRE_COMMIT_HOME)
- continueOnError: true
# pre-commit's venv doesn't allow user installs - not that they're really needed anyway.
- script: export PIP_USER=0; pre-commit run --all-files