Skip to content

Commit

Permalink
Added 2.2.2 version and removed 1.9.1
Browse files Browse the repository at this point in the history
  • Loading branch information
vfdev-5 authored Jun 14, 2024
1 parent f32e122 commit 0c4a212
Showing 1 changed file with 14 additions and 17 deletions.
31 changes: 14 additions & 17 deletions .github/workflows/pytorch-version-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
matrix:
python-version: [3.8, 3.9, "3.10"]
pytorch-version:
[2.1.2, 2.0.1, 1.13.1, 1.12.1, 1.11.0, 1.10.0, 1.9.1, 1.8.1, 1.5.1]
[2.2.2, 2.1.2, 2.0.1, 1.13.1, 1.12.1, 1.11.0, 1.10.0, 1.8.1, 1.5.1]
exclude:
- pytorch-version: 1.5.1
python-version: 3.9
Expand All @@ -31,9 +31,6 @@ jobs:
- pytorch-version: 1.8.1
python-version: "3.10"

- pytorch-version: 1.9.1
python-version: "3.10"

- pytorch-version: 1.10.0
python-version: "3.10"

Expand Down Expand Up @@ -100,16 +97,16 @@ jobs:
command: bash -l tests/run_cpu_tests.sh "not test_time_profilers"
new_command_on_retry: USE_LAST_FAILED=1 bash -l tests/run_cpu_tests.sh "not test_time_profilers"

# create-issue:
# runs-on: ubuntu-latest
# # https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#needs-context
# needs: build
# if: always() && needs.build.result == 'failure'
# steps:
# - uses: actions/checkout@v4
# - uses: JasonEtco/create-an-issue@v2
# name: Create issue if pytorch version tests failed
# with:
# filename: .github/failed_schedule_issue_template.md
# env:
# GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
create-issue:
runs-on: ubuntu-latest
# https://docs.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#needs-context
needs: build
if: always() && needs.build.result == 'failure'
steps:
- uses: actions/checkout@v4
- uses: JasonEtco/create-an-issue@v2
name: Create issue if pytorch version tests failed
with:
filename: .github/failed_schedule_issue_template.md
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

0 comments on commit 0c4a212

Please sign in to comment.