Skip to content

Conversation

jeffdaily
Copy link
Collaborator

Improves ROCm CI throughput by instantiating only for device tests that exercise the AMD GPU devices.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 31, 2021

💊 CI failures summary and remediations

As of commit 8a4c5e7 (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.

@jeffdaily
Copy link
Collaborator Author

jeffdaily commented Apr 1, 2021

Test Name Before PR After PR After PR 2nd try
test1 2 hr 35 min 1 hr 56 min 1 hr 50 min
test2 1 hr 33 min 1 hr 20 min 1 hr 56 min

Not sure why we're seeing such variation.

@github-actions github-actions bot added the ROCm label Apr 1, 2021
@codecov
Copy link

codecov bot commented Apr 1, 2021

Codecov Report

Merging #55069 (8a4c5e7) into master (a0ae3e5) will increase coverage by 17.03%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           master   #55069       +/-   ##
===========================================
+ Coverage   60.24%   77.28%   +17.03%     
===========================================
  Files         564     1893     +1329     
  Lines       69908   186474   +116566     
===========================================
+ Hits        42118   144118   +102000     
- Misses      27790    42356    +14566     

@jithunnair-amd jithunnair-amd added module: rocm AMD GPU support for Pytorch and removed ROCm labels Apr 2, 2021
Copy link
Collaborator

@jithunnair-amd jithunnair-amd left a comment

Choose a reason for hiding this comment

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

LGTM

@jithunnair-amd jithunnair-amd marked this pull request as ready for review April 2, 2021 02:56
@jithunnair-amd jithunnair-amd requested a review from malfet April 2, 2021 02:57
@jithunnair-amd
Copy link
Collaborator

Test Name Before PR After PR After PR 2nd try
test1 2 hr 35 min 1 hr 56 min 1 hr 50 min
test2 1 hr 33 min 1 hr 20 min 1 hr 56 min
Not sure why we're seeing such variation.

I took a look at the logs for test2; it seems that the unit test suites in the 2 logs are not exactly the same.

@facebook-github-bot
Copy link
Contributor

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

@facebook-github-bot
Copy link
Contributor

@malfet merged this pull request in 8e6e7dc.

pytorchmergebot pushed a commit that referenced this pull request May 3, 2022
This env var works similarly for both cuda and rocm builds.  Consider removing the ROCm-specific change in #55069 which came before the addition of this env var for cuda.
Pull Request resolved: #76668
Approved by: https://github.com/janeyx99
facebook-github-bot pushed a commit that referenced this pull request May 4, 2022
Summary:
This env var works similarly for both cuda and rocm builds.  Consider removing the ROCm-specific change in #55069 which came before the addition of this env var for cuda.

Pull Request resolved: #76668
Approved by: https://github.com/janeyx99

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/f1f29ac8b3cc3d7454a2d62cf0de525fe59eeeac

Reviewed By: malfet

Differential Revision: D36134095

fbshipit-source-id: 8a4a8473fbb1bc26caabcede3f2540e9d699a67b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants