Add missing data types at torch export serialization

[yintong-lu]

Related to #131654

Added missing FP8 data types at torch export serialization.
Added test cases of FP8 data types.

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @voznesenskym @penguinwu @EikanWang @Guobing-Chen @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov @xmfan

[pytorch-bot]

🔗 Helpful Links

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

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit d8fd395 with merge base 941da90 ():

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• inductor-rocm / rocm6.2-py3.10-inductor / test (inductor, 1, 2, linux.rocm.gpu.2) (gh) (similar failure)
  ##[error]Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
• inductor-rocm / rocm6.2-py3.10-inductor / test (inductor, 2, 2, linux.rocm.gpu.2) (gh) (similar failure)
  ##[error]Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

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

[jgong5]

It is a version downgrade from 8.1 to 7.3?

[yintong-lu]

Hi, I think this downgrade was due to an old version of main branch of my fork. I have reverted the changes on schema.yaml.
Could you please grant a CI approval? Thanks

[pytorch-bot]

Please seek CI approval before scheduling CIFlow labels

[yintong-lu]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Tried to rebase and push PR #138561, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

[yintong-lu]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

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

[angelayi]

could we follow this enumeration?

pytorch/c10/core/ScalarType.h

Lines 85 to 88 in b740a1b

	_(c10::Float8_e5m2, Float8_e5m2) /* 23 */ \
	_(c10::Float8_e4m3fn, Float8_e4m3fn) /* 24 */ \
	_(c10::Float8_e5m2fnuz, Float8_e5m2fnuz) /* 25 */ \
	_(c10::Float8_e4m3fnuz, Float8_e4m3fnuz) /* 26 */ \

[yintong-lu]

Hi Angela, I have made modifications accordingly.

[yintong-lu]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

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

[EikanWang]

@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

[facebook-github-bot]

@pytorchbot revert -m="Diff reverted internally" -c="ghfirst"

This Pull Request has been reverted by a revert inside Meta. To re-land this change, please open another pull request, assign the same reviewers, fix the CI failures that caused the revert and make sure that the failing CI runs on the PR by applying the proper ciflow label (e.g., ciflow/trunk).)

[pytorchmergebot]

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

[pytorchmergebot]

@yintong-lu your PR has been successfully reverted.

This PR was reopened (likely due to being reverted), so your approval was removed. Please request another review.

[guangyey]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

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