)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"24f44a9e8882d015856cef7b7484a8b07d638c7c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"ce4e2ace_15d03e29","updated":"2026-05-05 12:02:40.000000000","message":"lgtm it fixes the issues with the tests","commit_id":"c5edfd914d682aa13e77625789645dfc16f2d042"}],"tox.ini":[{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"24f44a9e8882d015856cef7b7484a8b07d638c7c","unresolved":false,"context_lines":[{"line_number":79,"context_line":"# eventlet deprecation warning messages breack output parsing. A more granular ignore"},{"line_number":80,"context_line":"# can not be done https://github.com/eventlet/eventlet/issues/1089"},{"line_number":81,"context_line":"setenv \u003d"},{"line_number":82,"context_line":"  PYTHONWARNINGS\u003dignore::Warning"},{"line_number":83,"context_line":"passenv \u003d OS_*"},{"line_number":84,"context_line":"commands \u003d"},{"line_number":85,"context_line":"  stestr --test-path\u003d./watcherclient/tests/client_functional/ run --concurrency\u003d1 {posargs}"}],"source_content_type":"text/x-properties","patch_set":4,"id":"bd2a1ac9_e926c359","line":82,"in_reply_to":"69edbc6a_c98d3cfe","updated":"2026-05-05 12:02:40.000000000","message":"\u003e PYTHONWARNINGS\u003dignore::Warning suppresses ALL warning categories, not just DeprecationWarning. A narrower filter like \u0027ignore::DeprecationWarning\u0027 would be more targeted.\n\u003e \n\u003e **Severity**: SUGGESTION | **Confidence**: 0.8\n\u003e \n\u003e **Benefit**: Suppressing only DeprecationWarning (or even just eventlet\u0027s specific warning class) would still allow other important warnings (FutureWarning, RuntimeWarning, etc.) to surface during functional tests, helping catch regressions earlier.\n\u003e \n\u003e **Recommendation**:\n\u003e Consider using \u0027PYTHONWARNINGS\u003dignore::DeprecationWarning\u0027 instead of \u0027ignore::Warning\u0027. If eventlet also emits FutureWarning or PendingDeprecationWarning, use multiple filters: \u0027ignore::DeprecationWarning,ignore::FutureWarning\u0027. The author has noted that granular filtering by module is not possible due to eventlet issue #1089, but filtering by warning type is still more precise than ignoring all warnings.\nAs mentioned in the commit message this suggestion does not work, I\u0027ve verified it in a devstack environment.","commit_id":"c5edfd914d682aa13e77625789645dfc16f2d042"}]}