From fd2723277a34803a7d0afbfae51e2ee74fa7f8a4 Mon Sep 17 00:00:00 2001 From: Alex Zorin Date: Sat, 1 Jul 2023 12:22:42 +1000 Subject: [PATCH] comment out PIP_USE_PEP517 --- .azure-pipelines/templates/steps/tox-steps.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.azure-pipelines/templates/steps/tox-steps.yml b/.azure-pipelines/templates/steps/tox-steps.yml index b20035aae..587f33b40 100644 --- a/.azure-pipelines/templates/steps/tox-steps.yml +++ b/.azure-pipelines/templates/steps/tox-steps.yml @@ -41,11 +41,11 @@ steps: python3 -m tox env: AWS_ACCESS_KEY_ID: $(AWS_ACCESS_KEY_ID) - AWS_SECRET_ACCESS_KEY: $(AWS_SECRET_ACCESS_KEY) + AWS_SECRET_ACCESS_KEY: $(AWS_SECRET_ACqCESS_KEY) AWS_EC2_PEM_FILE: $(testFarmPem.secureFilePath) # Enable --use-pep517 for pip. # As of pip 23.1.0, builds started failing on macOS unless this flag is set. - PIP_USE_PEP517: "true" + # PIP_USE_PEP517: "true" displayName: Run tox # For now, let's omit `set -e` and avoid the script exiting with a nonzero # status code to prevent problems here from causing build failures. If