Skip to content

fix: Add torchvision legacy CI parameter #1918

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
May 15, 2023

Conversation

gs-olive
Copy link
Collaborator

Description

  • Addresses nightly legacy CI failure

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • [ x ] My code follows the style guidelines of this project (You can use the linters)
  • [ x ] I have performed a self-review of my own code
  • [ x ] I have commented my code, particularly in hard-to-understand areas and hacks
  • [ x ] I have made corresponding changes to the documentation
  • [ x ] I have added tests to verify my fix or my feature
    • CI Testing
  • [ x ] New and existing unit tests pass locally with my changes
  • [ x ] I have added the relevant labels to my PR in so that relevant reviewers are notified

@gs-olive gs-olive self-assigned this May 13, 2023
@gs-olive gs-olive force-pushed the torchvision_legacy branch 11 times, most recently from b35d7ea to 4ed00ca Compare May 13, 2023 21:57
@gs-olive gs-olive force-pushed the torchvision_legacy branch from 4ed00ca to ddd2f01 Compare May 13, 2023 23:06
@gs-olive gs-olive changed the title minor fix: Add torchvision legacy CI parameter fix: Add torchvision legacy CI parameter May 15, 2023
Copy link
Collaborator

@narendasan narendasan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gs-olive gs-olive merged commit d4e5ed0 into pytorch:main May 15, 2023
@gs-olive gs-olive deleted the torchvision_legacy branch May 15, 2023 19:24
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants