From d1f9af444942276027bac8d932797d4ef4b291f0 Mon Sep 17 00:00:00 2001
From: Anna Henningsen <anna@addaleax.net>
Date: Sun, 23 Sep 2018 19:55:00 +0200
Subject: [PATCH] test: fix flaky sequential/test-fs-watch-system-limit

This test has at least once locally received `EMFILE` rather
than `ENOSPC`, which also seems to provide a reasonable error
message (which is what the test ultimately checks).
---
 test/sequential/test-fs-watch-system-limit.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/test/sequential/test-fs-watch-system-limit.js b/test/sequential/test-fs-watch-system-limit.js
index f7af3be86c29f4..e896cbf83b965a 100644
--- a/test/sequential/test-fs-watch-system-limit.js
+++ b/test/sequential/test-fs-watch-system-limit.js
@@ -42,7 +42,8 @@ gatherStderr.on('data', common.mustCallAtLeast((chunk) => {
   if (accumulated.includes('Error:') && !finished) {
     assert(
       accumulated.includes('ENOSPC: System limit for number ' +
-                           'of file watchers reached'),
+                           'of file watchers reached') ||
+      accumulated.includes('EMFILE: '),
       accumulated);
     console.log(`done after ${processes.length} processes, cleaning up`);
     finished = true;