test: add known issue test for path parse issue #6229

[jasnell]

Checklist

• make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
• tests and/or benchmarks are included
• commit message follows commit guidelines

Affected core subsystem(s)

known_issue

Description of change

Add known_issue test for #6229

[cjihrig]

Could you move this to the top, just under 'use strict;', and change Issue to Refs for consistency with the other known issue tests.

[cjihrig]

LGTM with a comment.

[jasnell]

Done. Also renamed the test file to be more specific.

[Trott]

Nit: Two tests in the file, one for path.posix.parse('/foo/bar/') and another for path.win32.parse('\\foo\\bar\\').

Nit: Instead of asserting that the two results are not equal, maybe make the test a bit more strict by asserting that each one equals exactly what it is supposed to equal?

assert.strictEqual(parsed1,{root: '/',dir: '/foo',base: 'bar',ext: '',name: 'bar'});assert.strictEqual(parsed2,{root: '/',dir: '/foo/bar',base: '',ext: '',name: ''});

If you're concerned that maybe we'll add another key to the object, you could do assertions specifically for the dir, base, and name properties.

[jasnell]

Updated.

[Trott]

LGTM

[jasnell]

Landed in 407069a
(Landed, then realized I'd completely missed doing a CI check... so retroactively... https://ci.nodejs.org/job/node-test-pull-request/3877/)

[MylesBorins]

@jasnell backport to v4x?