KEMBAR78
[REFACTOR] Factor _fx_graph_cache_key and _time_taken_ns to common base class by ezyang · Pull Request #141878 · pytorch/pytorch · GitHub
Skip to content

Conversation

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Dec 2, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (3 Unrelated Failures)

As of commit 9e410a3 with merge base a34a56f (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

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

ezyang added a commit that referenced this pull request Dec 2, 2024
…se class

Signed-off-by: Edward Z. Yang <ezyang@meta.com>

ghstack-source-id: 68267b9
Pull Request resolved: #141878
# TODO: Remove underscores here

# None if the output is not remote cacheable
_fx_graph_cache_key: Optional[str] = dataclasses.field(default=None, init=False)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we think this should be a method instead? And then have each implementation decide how to implement the method?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am still trying to understand how this field is populated, but my current impression is that we bong these attributes in no matter what concrete OutputCode subclass we have, so no, having it be a property under this design is probably fine.

@ezyang ezyang added ciflow/trunk Trigger trunk jobs on your pull request topic: not user facing topic category labels Dec 2, 2024
@ezyang
Copy link
Contributor Author

ezyang commented Dec 2, 2024

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

@albanD albanD removed their request for review December 2, 2024 19:43
@ezyang ezyang added the ci-no-td Do not run TD on this PR label Dec 3, 2024
pobin6 pushed a commit to pobin6/pytorch that referenced this pull request Dec 5, 2024
…se class (pytorch#141878)

Signed-off-by: Edward Z. Yang <ezyang@meta.com>

Pull Request resolved: pytorch#141878
Approved by: https://github.com/jamesjwu
ghstack dependencies: pytorch#141877
@github-actions github-actions bot deleted the gh/ezyang/3035/head branch January 2, 2025 02:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td Do not run TD on this PR ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: inductor topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants