From 00bdb6062796d47fdc11219028b2abca9c5c6f98 Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Fri, 23 Mar 2018 07:53:12 +0100 Subject: [PATCH] Ignore "Dropping message on closed channel." message This seems to happen with this test in tabs.feature with Qt 5.11: Scenario: :buffer with wrong argument (-1) It only happens ~1/50 times though, and seems like some Qt bug. See #3661 --- tests/end2end/fixtures/quteprocess.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/end2end/fixtures/quteprocess.py b/tests/end2end/fixtures/quteprocess.py index 41dee1275..e30dc03fa 100644 --- a/tests/end2end/fixtures/quteprocess.py +++ b/tests/end2end/fixtures/quteprocess.py @@ -200,6 +200,10 @@ def is_ignored_chromium_message(line): # [23359:23359:0319/115812.168578:WARNING: # render_frame_host_impl.cc(2744)] OnDidStopLoading was called twice. 'OnDidStopLoading was called twice.', + + # [30412:30412:0323/074933.387250:ERROR:node_channel.cc(899)] Dropping + # message on closed channel. + 'Dropping message on closed channel.', ] return any(testutils.pattern_match(pattern=pattern, value=message) for pattern in ignored_messages)