greenwave

#108 Add scenario values to the API response.
Merged by ralph. Opened by ralph.
scenario-in-api-response  into  master

Download 108.patch

At the request of @adamwill. Without this, it would be hard to
understand responses about failed rawhide composes.

How come it's just None in all the test cases?

I guess this is because the policies we are using in the test suite don't have any scenarios set, even though we must be using that in the prod policy... Do we need to update the test suite policies?

I guess this is because the policies we are using in the test suite don't have any scenarios set, even though we must be using that in the prod policy...

Mostly -- I did add a scenario'd test case requirement for compose.install_no_user in conf/policies/fedora.yaml.

1 new commit added

  • Ensure at least one test returns a non-None scenario in the response.

@dcallagh use of scenarios is fairly new (as in, the last few days) - @ralph added it after I pointed out it's necessary to distinguish between openQA results (where we quite often run the same test case on multiple media).

:thumbsup:

Nice :+1:

Pull-Request has been merged by ralph
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.