Coverage for nondeterministic_seeded, respect it in constant prop

[ezyang]

Stack from ghstack (oldest at bottom):

• Don't extract tensor metadata from sparse tensors #83669
• Refactor is_X_like, better invariant checking for SymInt overload #83668
• Refactor CppSignatureGroup to collect signatures as list. #83667
• -> Coverage for nondeterministic_seeded, respect it in constant prop #83650
• Be more conservative about propagating constants. #83648
• Address CR comments for "Delete ProxyTensor wrapper subclass" #83646

• nondeterministic_seeded was not applied to enough functions. I added
  some heuristics to codegen for identifying functions that are likely
  to be random and added a bunch of these tags to functions. Not sure
  I got all of them.

• Don't constant propagate through nondeterministic functions in FX
  tracing.

It would be better to do some testing for the tag but this would be quite an effort.

Signed-off-by: Edward Z. Yang ezyang@fb.com

[facebook-github-bot]

🔗 Helpful links

• 🧪  See artifacts and rendered test results at hud.pytorch.org/pr/83650
• 📄  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 our office hours

✅ No Failures (2 Pending)

As of commit 240d82b (more details on the Dr. CI page):

Expand to see more

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[bdhirsh]

lgtm!

[eellison]

LGTM... while you're at it maybe update this https://github.com/pytorch/pytorch/blob/master/torch/fx/passes/dialect/common/cse_pass.py#L14 to use the nondeterministic_seeded tag

[ezyang]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @ezyang.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.