Skip to content

[ROCm] add 4.1 to nightly builds #54635

New issue

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

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

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

jeffdaily
Copy link
Collaborator

Depends on pytorch/builder#685.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 24, 2021

💊 CI failures summary and remediations

As of commit 8a5793e (more details on the Dr. CI page):


💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

@codecov
Copy link

codecov bot commented Mar 25, 2021

Codecov Report

Merging #54635 (8a5793e) into master (d371a9f) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #54635      +/-   ##
==========================================
- Coverage   77.46%   77.46%   -0.01%     
==========================================
  Files        1893     1893              
  Lines      185939   185939              
==========================================
- Hits       144039   144029      -10     
- Misses      41900    41910      +10     

@ailzhang ailzhang added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Mar 25, 2021
@facebook-github-bot
Copy link
Contributor

@walterddr has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Copy link
Member

@seemethere seemethere left a comment

Choose a reason for hiding this comment

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

If we're going to add this should we remove 4.0.1?

@walterddr
Copy link
Contributor

good question. what's the policy here? should we keep 2 minor version for each major? (and when do we remove rocm3?)

@jeffdaily
Copy link
Collaborator Author

jeffdaily commented Mar 26, 2021

good question. what's the policy here? should we keep 2 minor version for each major? (and when do we remove rocm3?)

We would like to keep N, N-1, and N-2 versions available to users. This is in line with CI image policy, and aligns in general with the N-2 expectation we've discussed otherwise. This would mean today 4.1, 4.0.1, and 3.10.

As requested by @seemethere when we had 4.0 and 4.0.1 releases, patch releases replace the minor release they are replacing.

@malfet
Copy link
Contributor

malfet commented Mar 29, 2021

I agree with idea of keeping 3 most recent versions, but considering that first RoCM release was made against 4.0.1 (and there there are no torchvision for 3.10), we should keep building nightlies only for 4.0.1 and 3.10

@facebook-github-bot
Copy link
Contributor

@walterddr merged this pull request in 8cf97cb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Merged module: rocm AMD GPU support for Pytorch open source triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants