)]}'
{"futurist/tests/test_executors.py":[{"author":{"_account_id":10239,"name":"Dmitry Tantsur","email":"dtantsur@protonmail.com","username":"dtantsur"},"change_message_id":"9e32fbb55ddc070cbf624f20a34fe32221190c33","unresolved":false,"context_lines":[{"line_number":164,"context_line":"    def test_rejection(self):"},{"line_number":165,"context_line":"        ev \u003d self.event_cls()"},{"line_number":166,"context_line":"        ev_thread_started \u003d self.event_cls()"},{"line_number":167,"context_line":"        self.addCleanup(ev.set)"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"        def wait_until_set(check_delay):"},{"line_number":170,"context_line":"            ev_thread_started.set()"}],"source_content_type":"text/x-python","patch_set":2,"id":"7af24918_fba16f47","line":167,"updated":"2016-03-03 11:02:20.000000000","message":"so I\u0027m worried about ordering here.. it looks like in case of failures it will first try to run the 1st cleanup (shutdown) which will deadlock waiting for this second clean up.. maybe we should create this event and register its clean up in setUp?","commit_id":"9c41f416982ce36a04a1d14a6d3fa42eef18795f"},{"author":{"_account_id":1297,"name":"Joshua Harlow","email":"jxharlow@godaddy.com","username":"harlowja"},"change_message_id":"6247f038d579e0f3c736fa82b970623a1554f1dc","unresolved":false,"context_lines":[{"line_number":164,"context_line":"    def test_rejection(self):"},{"line_number":165,"context_line":"        ev \u003d self.event_cls()"},{"line_number":166,"context_line":"        ev_thread_started \u003d self.event_cls()"},{"line_number":167,"context_line":"        self.addCleanup(ev.set)"},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"        def wait_until_set(check_delay):"},{"line_number":170,"context_line":"            ev_thread_started.set()"}],"source_content_type":"text/x-python","patch_set":2,"id":"7af24918_31a91d91","line":167,"in_reply_to":"7af24918_fba16f47","updated":"2016-03-03 17:01:45.000000000","message":"Not true, from the testtools code,\n\n\u0027\u0027\u0027\nFunctions added with addCleanup will be called in reverse order of adding after tearDown, or after setUp if setUp raises an exception.\n\u0027\u0027\u0027\n\nhttps://github.com/testing-cabal/testtools/blob/master/testtools/testcase.py#L361\n\nSo event.set should happen first, then shutdown.","commit_id":"9c41f416982ce36a04a1d14a6d3fa42eef18795f"}]}