Skip to content

Fix EDM DPM Solver Test and Enhance Test Coverage #11679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mohiuddin-khan-shiam
Copy link

Changes

  • Fixed the previously skipped test_solver_order_and_type in test_scheduler_edm_dpmsolver_multistep.py
  • Properly separated testing of dpmsolver++ and sde-dpmsolver++ algorithms
  • Added comprehensive validation for all supported solver orders and types
  • Included output shape verification in test assertions
  • Improved error messages for better debugging

Testing

  • Verified all tests pass for both algorithm types
  • Confirmed proper handling of solver order constraints
  • Validated output shapes match expected dimensions

Impact

  • Improves test reliability for the EDM DPM Solver
  • Enhances maintainability with better test organization
  • Provides clearer feedback when tests fail

This PR resolves the previously skipped test_solver_order_and_type in the EDM DPM Solver tests by properly handling both dpmsolver++ and sde-dpmsolver++ algorithm types. The test now includes comprehensive validation for all supported solver orders and types, with improved error messages and additional assertions to verify output shapes. The changes ensure better test reliability and maintainability while providing clearer feedback for debugging.
@yiyixuxu
Copy link
Collaborator

can you take a look here? @DN6 @sayakpaul

@@ -527,14 +527,18 @@ def test_inference_batch_single_identical(
expected_max_diff=2e-3,
additional_params_copy_to_batched_inputs=["num_inference_steps"],
):
# Set default test behavior based on device
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nit): indentation?

Copy link
Member

@sayakpaul sayakpaul left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your PR. Can we break this into smaller PRs? For example, the scheduler related changes go sit in one, and the pipelines-related ones could sit in another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants