diff options
| author | Steve Dower <steve.dower@python.org> | 2023-01-11 17:25:46 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-11 17:25:46 +0000 |
| commit | 5ff029f7a30705ac00a1010d3d191edcd011f160 (patch) | |
| tree | 4e1518d4426d15771f004d5d2610543b0f05c0ee | |
| parent | 729ab9b622957fef0e9b494af9a71ab02986c741 (diff) | |
| download | cpython-git-5ff029f7a30705ac00a1010d3d191edcd011f160.tar.gz | |
Skip py.exe launcher tests in full layout CI test (GH-100948)
These tests become flaky when py.exe exists on the test machine but isn't the one that was just built. They also don't provide any useful information for this scenario, so easiest to just skip them.
| -rw-r--r-- | .azure-pipelines/windows-layout-steps.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.azure-pipelines/windows-layout-steps.yml b/.azure-pipelines/windows-layout-steps.yml index e15729fac3..afd8978179 100644 --- a/.azure-pipelines/windows-layout-steps.yml +++ b/.azure-pipelines/windows-layout-steps.yml @@ -12,7 +12,7 @@ steps: displayName: Show layout info (${{ parameters.kind }}) - ${{ if eq(parameters.fulltest, 'true') }}: - - script: .\python.exe -m test -q -uall -u-cpu -rwW --slowest --timeout=1200 -j0 --junit-xml="$(Build.BinariesDirectory)\test-results-${{ parameters.kind }}.xml" --tempdir "$(Build.BinariesDirectory)\tmp-${{ parameters.kind }}-$(arch)" + - script: .\python.exe -m test -q -uall -u-cpu -rwW --slowest --timeout=1200 -j0 --junit-xml="$(Build.BinariesDirectory)\test-results-${{ parameters.kind }}.xml" --tempdir "$(Build.BinariesDirectory)\tmp-${{ parameters.kind }}-$(arch)" -i test_launcher workingDirectory: $(Build.BinariesDirectory)\layout-${{ parameters.kind }}-$(arch) displayName: ${{ parameters.kind }} Tests env: |