KEMBAR78
Fix tune run not identifying custom components by RdoubleA · Pull Request #1617 · meta-pytorch/torchtune · GitHub
Skip to content

Conversation

@RdoubleA
Copy link
Collaborator

@RdoubleA RdoubleA commented Sep 17, 2024

Context

What is the purpose of this PR? Is it to

  • add a new feature
  • fix a bug
  • update tests and/or documentation
  • other (please add here)

Closes #1540

Test plan

Tested by creating a custom dataset builder and instantiating it in the config:

dataset:
  _component_: tune.dataset.custom_dataset

Then calling tune run with the fix, it was able to identify the custom component. Only works for single device, still figuring out with distributed doesn't work.

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 17, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 7909e48 with merge base 6b55c1d (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 17, 2024
@RdoubleA RdoubleA merged commit 1280744 into meta-pytorch:main Sep 17, 2024
17 checks passed
@RdoubleA RdoubleA deleted the fix_tune_run branch September 17, 2024 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Custom imports are broken

3 participants