)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":17887,"name":"Doug Schveninger","email":"ds6901@att.com","username":"Doug.Schveninger"},"change_message_id":"0cfc1efdcd8615a0731827e07536d52b976ca3a0","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Fix test_allowed_address_pair test case cleanup"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Make network cleanup to wait until its"},{"line_number":10,"context_line":"dependent ports are cleaned up"},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I91f5ced7873755081f94117c6a43bffcb85faab6"},{"line_number":13,"context_line":"Closes-bug: #1894835"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"9f560f44_9bff0233","line":10,"range":{"start_line":9,"start_character":0,"end_line":10,"end_character":30},"updated":"2020-09-09 04:37:12.000000000","message":"NIT: after reviewing the code I would think a detail description of the issue you are seeing would help out.  That way we understand the leak if the port does not delete fast enough.\n\nThe solution is to add a wait after the delete port.  Since addCleanup is LIFO execution the port delete will be called but the code will loop until the port is deleted so other issue will not happen.","commit_id":"a09be7e018c9e3b59cb4707b9146f336552b060d"}]}