test: mark a flaky test

test-inspector-port-cluster has been sometimes failing due to other processes running in our build machine and listening on ports 1025 and 1026. In order to successfully run in a variety of machine states, this test must be marked as flaky. PR-URL: #480 Reviewed-By: Kyle Farnung <[email protected]>
nodejs · Feb 26, 2018 · b775305 · b775305
1 parent 8d6c6f5
commit b775305
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/test/sequential/sequential.status b/test/sequential/sequential.status
@@ -40,6 +40,10 @@ test-inspector-contexts : SKIP
 test-inspector-scriptparsed-context : SKIP
 test-inspector-stop-profile-after-done : SKIP
 
+[$jsEngine==chakracore && $system==win32]
+# This test can fail depending on the ports that other processes are using
+test-inspector-port-cluster : PASS, FLAKY
+
 [$jsEngine==chakracore && $system==linux]
 # These tests are failing for Node-Chakracore and should eventually be fixed
 test-child-process-pass-fd : SKIP