🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/116305

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit d8017ae with merge base 946e202 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

I think I need approval to keep debugging with the CI please

I added you to the repo, that should durably give you rights

Thx, this is my current error in the CI, I don't get it. Can anyone provide some insight please ?

distributed/test_store 1/1 failed! Received signal: SIGIOT
Emiting td_test_failure_stats
could not find path /var/lib/jenkins/workspace/.additional_ci_files/previous_failures.json
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/run_test.py", line 1812, in <module>
    main()
  File "/var/lib/jenkins/workspace/test/run_test.py", line 1764, in main
    run_tests(
  File "/var/lib/jenkins/workspace/test/run_test.py", line 1620, in run_tests
    raise RuntimeError(failure.message)
RuntimeError: distributed/test_store 1/1 failed! Received signal: SIGIOT

I launched the CI again in case it's a dud.

It might just be flaky master, check what dr ci says (i can't see it anymore since you repushed)

This now passes. Please review :)

@mingfeima will you be reviewing this?

btw, don't say fix #59168 in the PR description if you don't intend to let the PR close the issue

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

I still think this is relevant.

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

I guess those are user facing, no ? @ezyang

They would maybe need a comment saying something like : "3D pooling is now compatible with channels last tensors".

@pytorchbot merge

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: 2 jobs have failed, first few of them are: trunk / win-vs2019-cpu-py3 / test (default, 2, 3, windows.4xlarge.nonephemeral), trunk / linux-focal-rocm5.7-py3.8 / test (default, 1, 1, linux.rocm.gpu)

@pytorchbot merge -r

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Successfully rebased 3d_channels_last_pooling_3 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout 3d_channels_last_pooling_3 && git pull --rebase)

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team