Test sigmas in PipelineTesterMixin

[SahilCarterr]

What does this PR do?

Added sigmas test for FluxPipelines

Continuation of Issues #10071 and #10081
Adding Test for PR #10081

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline?
• Did you read our philosophy doc (important for complex PRs)?
• Was this discussed/approved via a GitHub issue or the forum? Please add a link to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed.
@yiyixuxu

[hlky]

Thanks @SahilCarterr! I think we can add this to the PipelineTesterMixin so it works with all supported pipelines.

diffusers/tests/pipelines/test_pipelines_common.py

Line 874 in 63b631f

classPipelineTesterMixin:

diffusers/tests/pipelines/test_pipelines_common.py

Lines 1700 to 1719 in 63b631f

	deftest_cfg(self):
	sig=inspect.signature(self.pipeline_class.__call__)
	if"guidance_scale"notinsig.parameters:
	return
	components=self.get_dummy_components()
	pipe=self.pipeline_class(**components)
	pipe=pipe.to(torch_device)
	pipe.set_progress_bar_config(disable=None)
	inputs=self.get_dummy_inputs(torch_device)
	inputs["guidance_scale"] =1.0
	out_no_cfg=pipe(**inputs)[0]
	inputs["guidance_scale"] =7.5
	out_cfg=pipe(**inputs)[0]
	assertout_cfg.shape==out_no_cfg.shape

cc @sayakpaul@DN6 WDYT? We currently test this for AYS schedule on stable_diffusion and stable_diffusion_xl pipelines

diffusers/tests/pipelines/stable_diffusion/test_stable_diffusion.py

Line 262 in 63b631f

deftest_stable_diffusion_ays(self):

[sayakpaul]

cc @sayakpaul@DN6 WDYT? We currently test this for AYS schedule on stable_diffusion and stable_diffusion_xl pipelines

Indeed! Perhaps a better way to cover scheduler compatibility for pipelines would be to define a known scheduler support matrix somewhere at the top of the test_pipelines_common and loop through it. But this is just an idea and I am okay if we want to do it in some other way.

[hlky]

@SahilCarterr would you like to move this test into PipelineTesterMixin? or I can take over if you'd prefer.

[hlky]

@SahilCarterr Thanks for moving the test! Looks like some changes to example notebooks got added to this PR, could we remove that?

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[SahilCarterr]

Just removed it. Notebooks were added due to make style and quality

[hlky]

Looks like this has revealed issues with some pipelines, I've found similar issues adding a test for timesteps. I'll work through them to determine if the argument is unsupported (due to required scheduler etc.) or if there's something to be fixed.

[SahilCarterr]

Thank you for the update and for looking into these issues and further Continuing this PR ! I appreciate your efforts in working through them. @hlky