Fer2013.py issue

[real-ojaswi]

fer2013.py has been updated to provide test labels as well given the correct fer2013.csv is present in the root directory. If not, the functionality will be same as the current version with an added warning that test labels will not be provided.

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 8 New Failures

As of commit 3ef3c4b with merge base 61d97f4 ():

NEW FAILURES - The following jobs have failed:

• CMake / macos (macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-linux (3.9, linux.12xlarge, cpu) / linux-job (gh)
  RuntimeError: DGifOpenFileName() failed - 103
• Tests / unittests-macos (3.10, macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-macos (3.11, macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-macos (3.12, macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-macos (3.8, macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-macos (3.9, macos-12) / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 1
• Tests / unittests-windows (3.8, windows.4xlarge, cpu) / windows-job (gh)
  test/test_datasets.py::LFWPairsTestCase::test_transforms

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

[facebook-github-bot]

Hi @real-ojaswi!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

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 [email protected]. Thanks!

[real-ojaswi]

#8368 #8118 is addressed here.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[NicolasHug]

Thanks for the PR @real-ojaswi . This was already partly addressed in #8368 but that PR was stalled. Yours was good too but a few changes were necessary - since i'm a bit short of resources right now I've decided to address the changes myself in #8452. Thank you for contributing!