MM Eval tests

[SalmanMohammadi]

Context

What is the purpose of this PR? Is it to

• add a new feature
• fix a bug
• update tests and/or documentation
• other (please add here)

Please link to any issues this PR addresses.

Adds some tests for the eval recipe using dummy Llama3.2 Vision models.

Test plan

Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.

• run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
• add unit tests for any new functionality
• update docstrings for any new or updated methods or classes
• run unit tests via pytest tests
• run recipe tests via pytest tests -m integration_test
• manually run any new or modified recipes with sufficient proof of correctness
• include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example

• I did not change any public API
• I have added an example to docs or docstrings

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

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

[RdoubleA]

we have this in tests/torchtune/modules/test_common_utils.py, opportunity to unify?

[SalmanMohammadi]

It made the most sense to me to define the fixture where it was being used - do you have strong opinions here?

[joecummings]

How did our linter not pick this up...

[SalmanMohammadi]

holy moly

 ============================= slowest 20 durations =============================
376.79s call     tests/recipes/test_eleuther_eval.py::TestEleutherEval::test_meta_eval_vision
342.01s call     tests/recipes/test_eleuther_eval.py::TestEleutherEval::test_hf_eval_vision

I fix

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 32.30769% with 44 lines in your changes missing coverage. Please review.

Project coverage is 24.78%. Comparing base (9eced21) to head (ed3f02e).
Report is 19 commits behind head on main.

Files with missing lines	Patch %	Lines
tests/recipes/test_eleuther_eval.py	35.29%	33 Missing ⚠️
tests/recipes/utils.py	21.42%	11 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #1887       +/-   ##
===========================================
- Coverage   68.40%   24.78%   -43.62%     
===========================================
  Files         311      318        +7     
  Lines       16973    17649      +676     
===========================================
- Hits        11610     4375     -7235     
- Misses       5363    13274     +7911     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[SalmanMohammadi]

I DONT understand why this is failing, it's passing locally

[SalmanMohammadi]

im so done