Properly propagates checkpoint wrapper args and kwargs

[dirkgr]

It looks like passing *args and **kwargs to checkpoint_wrapper() does not work because someone forgot some *s. This adds them back in.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Degradation on most runner types due to networking outage

❌ 1 New Failure

As of commit e19332e:

NEW FAILURE - The following job has failed:

• BC Lint (gh)

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dirkgr / name: Dirk Groeneveld (3e69a32)

[awgu]

Good catch! Let us see how CI responds in case we need to adjust any unit tests (that might have been passing due to the args/kwargs not propagating).

[awgu]

@dirkgr Could you sign the CLA?

[dirkgr]

I sent it to my manager. I assume he'll sign it on Monday.

[dirkgr]

It is done.

[kit1980]

If nothing on the CI fails after the change, then it would be really nice to add a test for this.

[awgu]

#100576

[awgu]

@pytorchbot merge

[pytorch-bot]

This PR needs to be approved by an authorized maintainer before merge.

[awgu]

@pytorchbot merge

[pytorchmergebot]

Merge failed

Reason: This PR needs a 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.

Details for Dev Infra team

Raised by workflow job

[awgu]

@pytorchbot merge

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: This PR is too stale; the last push date was more than 3 days ago. Please rebase and try again. You can rebase and merge by leaving the following comment on this PR:
@pytorchbot merge -r
Or just rebase by leaving @pytorchbot rebase comment

Details for Dev Infra team

Raised by workflow job

[awgu]

@pytorchbot merge -r

[pytorchmergebot]

@pytorchbot successfully started a rebase job. Check the current status here

[pytorchmergebot]

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

[pytorchmergebot]

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

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

• pull / win-vs2019-cpu-py3 / build

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[kit1980]

@pytorchbot merge -ic

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 1 checks: pull / win-vs2019-cpu-py3 / build

Learn more about merging in the wiki.

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

Advanced Debugging

Check the merge workflow status
here