Skip to content

Conversation

@r-barnes
Copy link
Contributor

Test Plan: Sandcastle

Differential Revision: D35194795

Test Plan: Sandcastle

Differential Revision: D35194795

fbshipit-source-id: 15bcd27feb7f1e0886ec7d8432c439999b9f25bc
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 29, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 3ff9f8c (more details on the Dr. CI page):


  • 1/1 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

See GitHub Actions build pull / linux-bionic-rocm4.5-py3.7 / test (default, 2, 2, linux.rocm.gpu) (1/1)

Step: "Test" (full log | diagnosis details | 🔁 rerun)

2022-03-29T22:02:51.7138257Z FAIL [0.013s]: test_caching_pinned_memory (__main__.TestCuda)
2022-03-29T22:02:51.7058423Z   test_scatter_cpu_dim (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7066055Z   test_scatter_cpu_neg_dim (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7072113Z   test_scatter_cpu_sizes (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7080262Z   test_scatter_gpu (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7087597Z   test_scatter_gpu_dim (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7094695Z   test_scatter_gpu_neg_dim (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7102522Z   test_scatter_gpu_sizes (__main__.TestCudaComm) ... skip: only one GPU detected (0.001s)
2022-03-29T22:02:51.7136844Z   test_scatter_namedtuple (__main__.TestCudaComm) ... skip: Test needs multiple GPUs (0.003s)
2022-03-29T22:02:51.7137389Z 
2022-03-29T22:02:51.7137646Z ======================================================================
2022-03-29T22:02:51.7138257Z FAIL [0.013s]: test_caching_pinned_memory (__main__.TestCuda)
2022-03-29T22:02:51.7144448Z ----------------------------------------------------------------------
2022-03-29T22:02:51.7145468Z Traceback (most recent call last):
2022-03-29T22:02:51.7146971Z   File "/opt/conda/lib/python3.7/site-packages/torch/testing/_internal/common_utils.py", line 1780, in wrapper
2022-03-29T22:02:51.7148016Z     method(*args, **kwargs)
2022-03-29T22:02:51.7148869Z   File "test_cuda.py", line 1370, in test_caching_pinned_memory
2022-03-29T22:02:51.7150221Z     self.assertNotEqual(t.data_ptr(), ptr, msg='allocation re-used too soon')
2022-03-29T22:02:51.7151943Z   File "/opt/conda/lib/python3.7/site-packages/torch/testing/_internal/common_utils.py", line 2189, in assertNotEqual
2022-03-29T22:02:51.7153493Z     self.assertEqual(x, y, msg, atol=atol, rtol=rtol, **kwargs)
2022-03-29T22:02:51.7154845Z AssertionError: AssertionError not raised : allocation re-used too soon
2022-03-29T22:02:51.7155499Z 

This comment was automatically generated by Dr. CI (expand for details).

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

Click here to manually regenerate this comment.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D35194795

facebook-github-bot pushed a commit that referenced this pull request Mar 30, 2022
Summary: Pull Request resolved: #74918

Test Plan: Sandcastle

Reviewed By: ngimel

Differential Revision: D35194795

fbshipit-source-id: 8490e5497c37bab0055925ed520c2fd0c37a554c
@github-actions
Copy link
Contributor

Hey @r-barnes.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants