test: uv_tty_init now returns EINVAL on IBM i

Since the PR libuv/libuv#2753 has been landed, we need to revert the code change in PR #32338. PR-URL: #33629 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
nodejs · Jun 18, 2020 · 15eb5a3 · 15eb5a3
1 parent c3728c6
commit 15eb5a3
Showing 1 changed file with 4 additions and 5 deletions.
diff --git a/test/parallel/test-ttywrap-invalid-fd.js b/test/parallel/test-ttywrap-invalid-fd.js
@@ -21,14 +21,13 @@ assert.throws(
 
 {
   const info = {
-    code: common.isWindows || common.isIBMi ? 'EBADF' : 'EINVAL',
-    message: common.isWindows ||
-      common.isIBMi ? 'bad file descriptor' : 'invalid argument',
-    errno: common.isWindows || common.isIBMi ? UV_EBADF : UV_EINVAL,
+    code: common.isWindows ? 'EBADF' : 'EINVAL',
+    message: common.isWindows ? 'bad file descriptor' : 'invalid argument',
+    errno: common.isWindows ? UV_EBADF : UV_EINVAL,
     syscall: 'uv_tty_init'
   };
 
-  const suffix = common.isWindows || common.isIBMi ?
+  const suffix = common.isWindows ?
     'EBADF (bad file descriptor)' : 'EINVAL (invalid argument)';
   const message = `TTY initialization failed: uv_tty_init returned ${suffix}`;