Add stateful dl import to smoke test

[gokulavasan]

title

Fixes #{issue number}

Changes

[atalman]

Please throw exception here if torchdata.__version__ != 0.8.0
We would need to route it later via input parameter. However this can be a followup PR

[atalman]

please address comment and we are good to merge

[gokulavasan]

@atalman Is that change what you had in mind? Can you also confirm if it is fine to land this in main branch (with the check being about 0.8.0) and the cherry pick this to release/0.8 branch?

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 14 New Failures

As of commit f4d0986 with merge base de5791b ():

NEW FAILURES - The following jobs have failed:

• Build Linux Conda / pytorch/data / upload / conda-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• Build Linux Wheels / pytorch/data / upload / manywheel-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• Build M1 Conda / pytorch/data / upload / conda-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• Build M1 Wheels / pytorch/data / upload / wheel-py3_8-cpu (gh)
  Unable to find any artifacts for the associated workflow
• Validate binaries / validate-binaries / linux-manywheel-3.10-rocm6.0 / linux-manywheel-3.10-rocm6.0 (gh)
  RuntimeError: Command docker exec -t 09c6c8a112b06eebe8649f1e0319643df23253f28e4fdae8b7eb71dc287404d6 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.10-rocm6.1 / linux-manywheel-3.10-rocm6.1 (gh)
  RuntimeError: Command docker exec -t 95d0f7b4828e47db5d5fb2299e4f7e4ff4072c9e3d0d6df229a705dd269e9040 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.11-rocm6.0 / linux-manywheel-3.11-rocm6.0 (gh)
  RuntimeError: Command docker exec -t 37d8e256c1880d6917b83d0c37c80e8361629dd16d72ad034e579c4f399161fb /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.11-rocm6.1 / linux-manywheel-3.11-rocm6.1 (gh)
  RuntimeError: Command docker exec -t de65c92a52c05f81487bb932de43b2875e18b593822353204aab85b2457dc9cb /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.12-rocm6.0 / linux-manywheel-3.12-rocm6.0 (gh)
  RuntimeError: Command docker exec -t 8c087606e39fcc4a1bf98ddf2e19680ad1d8cfd230b70f8a9359501575154f78 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.12-rocm6.1 / linux-manywheel-3.12-rocm6.1 (gh)
  RuntimeError: Command docker exec -t 9dce8eb9e69b48a81cf42378e9bd1022474882eea86f2f4f371b283f2a1b52fd /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.8-rocm6.0 / linux-manywheel-3.8-rocm6.0 (gh)
  RuntimeError: Command docker exec -t b1caaef0341439fdc89244b4bc39aa8a297d4cdf55b5a695723d560d71a7e9d2 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.8-rocm6.1 / linux-manywheel-3.8-rocm6.1 (gh)
  RuntimeError: Command docker exec -t ffe6e42437fa444b5cc279eb2ed2b510b6e112cf847536ec2fdedf816618a672 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.9-rocm6.0 / linux-manywheel-3.9-rocm6.0 (gh)
  RuntimeError: Command docker exec -t 6d1286dbc9a23aea943a91803770517b4e96137bda5f6f69829c2a316a3c57c9 /exec failed with exit code 1
• Validate binaries / validate-binaries / linux-manywheel-3.9-rocm6.1 / linux-manywheel-3.9-rocm6.1 (gh)
  RuntimeError: Command docker exec -t 5f98cb7f03608faf18139ee2b844f4714f0da34b4dc3ec21f0912be71aa8da34 /exec failed with exit code 1

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

[meta-cla]

Hi @gokulavasan!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!