test: rename test-regress-GH-4027
Rename the test appropriately alongside mentioning the subsystem Also, make a few basic changes to make sure the test conforms to the standard test structure Refs: https://github.com/nodejs/node/issues/19105 Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure PR-URL: https://github.com/nodejs/node/pull/19161 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
This commit is contained in:
parent
73630e6aaa
commit
d0518c28ce
@ -21,6 +21,17 @@
|
||||
|
||||
'use strict';
|
||||
const common = require('../common');
|
||||
|
||||
// Make sure the deletion event gets reported in the following scenario:
|
||||
// 1. Watch a file.
|
||||
// 2. The initial stat() goes okay.
|
||||
// 3. Something deletes the watched file.
|
||||
// 4. The second stat() fails with ENOENT.
|
||||
|
||||
// The second stat() translates into the first 'change' event but a logic error
|
||||
// stopped it from getting emitted.
|
||||
// https://github.com/nodejs/node-v0.x-archive/issues/4027
|
||||
|
||||
const assert = require('assert');
|
||||
const path = require('path');
|
||||
const fs = require('fs');
|
Loading…
x
Reference in New Issue
Block a user