Skip to content

Conversation

Chillee
Copy link
Collaborator

@Chillee Chillee commented Oct 3, 2024

Summary: making it so that the config can pass config.activation_memory_budget_solver as a callable method and then that callable is invoked to determine the set of saved/recomputed nodes.

Test Plan: tbd

Reviewed By: Chillee, basilwong

Differential Revision: D63714905

Copy link

pytorch-bot bot commented Oct 3, 2024

🔗 Helpful Links

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

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

❌ 2 New Failures

As of commit f7b8d36 with merge base f4b415d (image):

NEW FAILURES - The following jobs have failed:

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

@facebook-github-bot
Copy link
Contributor

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

@Chillee Chillee added the topic: not user facing topic category label Oct 3, 2024
Chillee pushed a commit to Chillee/pytorch that referenced this pull request Oct 4, 2024
…e SOLVER as a callable (pytorch#137314)

Summary:

making it so that the config can pass `config.activation_memory_budget_solver` as a callable method and then that callable is invoked to determine the set of saved/recomputed nodes.

Test Plan: tbd

Reviewed By: Chillee, basilwong

Differential Revision: D63714905
@facebook-github-bot
Copy link
Contributor

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

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 4, 2024
@paryxyt paryxyt requested a review from basilwong October 4, 2024 19:45
saved_node_idx, recomp_node_idx = SOLVER(
memory, joint_graph, max_memory, node_info, all_recomputable_banned_nodes
)
return (0.0, saved_node_idx, recomp_node_idx)
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice, will rebase changes onto tuple

Chillee pushed a commit to Chillee/pytorch that referenced this pull request Oct 4, 2024
…e SOLVER as a callable (pytorch#137314)

Summary:

making it so that the config can pass `config.activation_memory_budget_solver` as a callable method and then that callable is invoked to determine the set of saved/recomputed nodes.

Test Plan: tbd

Reviewed By: Chillee, basilwong

Differential Revision: D63714905
@facebook-github-bot
Copy link
Contributor

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

…e SOLVER as a callable (pytorch#137314)

Summary:

making it so that the config can pass `config.activation_memory_budget_solver` as a callable method and then that callable is invoked to determine the set of saved/recomputed nodes.

Test Plan: tbd

Reviewed By: Chillee, basilwong

Differential Revision: D63714905
@facebook-github-bot
Copy link
Contributor

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

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@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

@pytorchmergebot
Copy link
Collaborator

Merge failed

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

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@huydhn
Copy link
Contributor

huydhn commented Oct 9, 2024

@pytorchbot merge -f 'I need to merge this to fix ShipIt, however, might need to revert this after if it breaks trunk'

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

@huydhn
Copy link
Contributor

huydhn commented Oct 9, 2024

@pytorchbot revert -m 'The failure shows up in trunk' -c ignoredsignal

functorch/test_ac.py::MemoryBudgetTest::test_attention_vs_linear GH job link HUD commit link

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchmergebot
Copy link
Collaborator

@Chillee your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Oct 9, 2024
…commodate SOLVER as a callable (#137314)"

This reverts commit 932b994.

Reverted #137314 on behalf of https://github.com/huydhn due to The failure shows up in trunk ([comment](#137314 (comment)))
Copy link
Contributor

github-actions bot commented Dec 8, 2024

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.

@github-actions github-actions bot added the Stale label Dec 8, 2024
@github-actions github-actions bot closed this Jan 7, 2025
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.

7 participants