just skip the new matplotlib tests on CI

they pass locally, so keep the tests, but don't keep holding up release with slow, flaky tests

Author: minrk

tests/test_matplotlib_eventloops.py

@@ -9,9 +9,10 @@
 from .utils import assemble_output
 
 # these tests don't seem to work with xvfb yet
+# these tests seem to be a problem on CI in general
 pytestmark = pytest.mark.skipif(
-    sys.platform == "linux" and bool(os.getenv("CI")),
-    reason="tests not working yet with xvfb on linux CI",
+    bool(os.getenv("CI")),
+    reason="tests not working yet reliably on CI",
 )
 
 guis = []
@@ -45,13 +46,6 @@ def execute(
 def test_matplotlib_gui(kc, gui):
     """Make sure matplotlib activates and its eventloop runs while the kernel is also responsive"""
     pytest.importorskip("matplotlib", reason="this test requires matplotlib")
-    if (
-        gui == "qt"
-        and os.getenv("QT") == "qt5"
-        and os.getenv("CI")
-        and sys.platform.startswith("win")
-    ):
-        pytest.skip("flaky on Windows CI")
     stdout, stderr = execute(kc, f"%matplotlib {gui}")
     assert not stderr
     # debug: show output from invoking the matplotlib magic