From 0c7e55d80cfaaaf2125a1423671a8319511e4e91 Mon Sep 17 00:00:00 2001 From: bcoe Date: Mon, 12 Oct 2020 10:42:13 -0700 Subject: [PATCH] test: rimraf fix seems to have fixed known issue --- test/known_issues/known_issues.status | 3 +-- test/{known_issues => parallel}/test-fs-open-no-close.js | 7 ------- 2 files changed, 1 insertion(+), 9 deletions(-) rename test/{known_issues => parallel}/test-fs-open-no-close.js (62%) diff --git a/test/known_issues/known_issues.status b/test/known_issues/known_issues.status index 01a82246c93fcb..e0f0a456089bf2 100644 --- a/test/known_issues/known_issues.status +++ b/test/known_issues/known_issues.status @@ -1,3 +1,4 @@ + prefix known_issues # If a known issue does not apply to a platform, list the test name in the @@ -27,5 +28,3 @@ test-vm-timeout-escape-queuemicrotask: SKIP # The Raspberry Pis are too slow to run this test. # See https://github.com/nodejs/build/issues/2227#issuecomment-608334574 test-crypto-authenticated-stream: SKIP -# The bug being checked is that the test never exits. -test-fs-open-no-close: TIMEOUT diff --git a/test/known_issues/test-fs-open-no-close.js b/test/parallel/test-fs-open-no-close.js similarity index 62% rename from test/known_issues/test-fs-open-no-close.js rename to test/parallel/test-fs-open-no-close.js index ef990d1a67df83..5e432dd11d8084 100644 --- a/test/known_issues/test-fs-open-no-close.js +++ b/test/parallel/test-fs-open-no-close.js @@ -4,14 +4,7 @@ // Failing to close a file should not keep the event loop open. const common = require('../common'); - -// This issue only shows up on Raspberry Pi devices in our CI. When this test is -// moved out of known_issues, this check can be removed, as the test should pass -// on all platforms at that point. const assert = require('assert'); -if (process.arch !== 'arm' || process.config.variables.arm_version > 7) { - assert.fail('This test is for Raspberry Pi devices in CI'); -} const fs = require('fs');