Skip to content

src: write named pipe info in diagnostic report #38637

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
legendecas wants to merge 10 commits into from
Closed

src: write named pipe info in diagnostic report #38637

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
534db1a
src: write named pipe info in diagnostic report
legendecas May 11, 2021
74b1e3e
fixup! src: write named pipe info in diagnostic report
legendecas May 12, 2021
5dd9185
fixup! src: write named pipe info in diagnostic report
legendecas May 12, 2021
477e50f
fixup! src: write named pipe info in diagnostic report
legendecas May 16, 2021
0efa117
fixup! test: windows fanned test failed
legendecas May 17, 2021
69d3ea5
fixup! test: windows fanned test failed
legendecas May 17, 2021
6451d80
fixup! test: windows fanned test failed
legendecas May 18, 2021
0112fba
fixup! test: windows fanned test failed
legendecas May 19, 2021
14e0b9a
fixup! merge with common.PIPE
legendecas May 19, 2021
d5d6ee7
fixup! test: windows fanned test failed
legendecas May 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
fixup! test: windows fanned test failed 
various pipe connect API failed in parallel/test-net-connect-options-path.
  • Loading branch information
@legendecas
legendecas committed May 19, 2021
commit d5d6ee71b152c9e3f943f5d5cb030b4a04b30d7d
2 changes: 1 addition & 1 deletion test/common/index.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,7 @@ const localIPv6Hosts =

const PIPE = (() => {
const localRelative = path.relative(process.cwd(), `${tmpdir.path}/`);
const pipePrefix = isWindows ? '\\\\?\\pipe\\' : localRelative;
const pipePrefix = isWindows ? '\\\\.\\pipe\\' : localRelative;
const pipeName = `node-test.${process.pid}.sock`;
return path.join(pipePrefix, pipeName);
})();
Expand Down
12 changes: 11 additions & 1 deletion test/report/test-report-uv-handles.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,19 @@
// Testcase to check reporting of uv handles.
const common = require('../common');
const tmpdir = require('../common/tmpdir');
Comment thread
richardlau marked this conversation as resolved.
const path = require('path');
if (common.isIBMi)
common.skip('IBMi does not support fs.watch()');

// This is quite similar to common.PIPE except that it uses an extended prefix
// of "\\?\pipe" on windows.
const PIPE = (() => {
const localRelative = path.relative(process.cwd(), `${tmpdir.path}/`);
const pipePrefix = common.isWindows ? '\\\\?\\pipe\\' : localRelative;
const pipeName = `node-test.${process.pid}.sock`;
return path.join(pipePrefix, pipeName);
})();

function createFsHandle(childData) {
const fs = require('fs');
// Watching files should result in fs_event/fs_poll uv handles.
Expand Down Expand Up @@ -90,7 +100,7 @@ function createUdpHandle(childData) {

function createNamedPipeHandle(childData) {
const net = require('net');
const sockPath = common.PIPE;
const sockPath = PIPE;
return new Promise((resolve) => {
const server = net.createServer((socket) => {
childData.pipe_sock_path = server.address();
Expand Down