)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"fc78491e689b5483291ea7820f81fb9d76cf7957","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0aec4d9c_00aa77f4","updated":"2026-08-13 12:20:41.000000000","message":"Still missing API tests, which is going to be added soon","commit_id":"d706c421e96c8ed3444a9a41c3d46463284e0679"}],"watcher_tempest_plugin/tests/scenario/base.py":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"d9daf1b4fc01504787f6d2fe39a15b16d8dfeedd","unresolved":false,"context_lines":[{"line_number":1034,"context_line":"                    pipeline[\u0027uuid\u0027]),"},{"line_number":1035,"context_line":"                duration\u003d600,"},{"line_number":1036,"context_line":"                sleep_for\u003d2,"},{"line_number":1037,"context_line":"            ))"},{"line_number":1038,"context_line":"        except ValueError:"},{"line_number":1039,"context_line":"            self.fail(\"The audit pipeline has failed!\")"},{"line_number":1040,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"29495320_54cd107d","line":1037,"updated":"2026-08-12 23:56:16.000000000","message":"The create_audit_pipeline_and_wait method in scenario/base.py uses hardcoded duration\u003d600 and sleep_for\u003d2, and wait_for_pipeline in common/base.py uses a hardcoded default timeout\u003d600 and sleep_for\u003d2. The immediately preceding commit (5ef3d55) specifically replaced all hardcoded duration/sleep_fo...\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Operators and CI engineers cannot tune pipeline wait timeouts via configuration. A pipeline that takes longer than 600 seconds will always fail, even if the deployment needs a higher timeout. The configurable options were introduced specifically to address this class of problem.\n\n**Suggestion**:\nReplace hardcoded duration\u003d600 with CONF.optimize.resource_timeout and sleep_for\u003d2 with CONF.optimize.resource_check_interval in both create_audit_pipeline_and_wait (scenario/base.py) and wait_for_pipeline (common/base.py). The wait_for_pipeline signature could accept an optional timeout that defaults to CONF.optimize.resource_timeout.","commit_id":"d706c421e96c8ed3444a9a41c3d46463284e0679"}]}