Repository navigation
test-debug-uncaught-exception-async fails on Win2012 #18454
Copy link
Copy link
Closed
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
Description
- Version: 6.12.4-pre (but seen on previous v6.x versions)
- Platform: Win 2012 (not R2)
- Subsystem: test
This failure is only seen on Windows Server 2012 (not 2012 R2) - see #18177. I see the failure intermittently on my Win2012 machine. On the Win2012 Azure machine provisioned by @joaocgreis the test fails every time with the same error.
I cannot reproduce this failure on any Win2012 R2 machines.
parallel/test-debug-uncaught-execption-async fails with the following error:
...
not ok 217 parallel/test-debug-uncaught-exception-async
---
duration_ms: 0.882
severity: fail
stack: |-
assert.js:85
throw new assert.AssertionError({
^
AssertionError: 7 === 1
at ChildProcess.result.on (D:\build\jenkins-new\v6tstwin\x86node\node\test\parallel\test-debug-uncaught-exception-async.js:19:10)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:498:12)
...
When running fixtures/debug-uncaught-async.js separately, on Win2012 I hit the following error:
debug> (node:3900) There was an internal error in Node's debugger. Please report this bug.
fhqwhgads
Error: fhqwhgads
at Immediate.emit (C:\Users\node\Desktop\node\test\fixtures\debug-uncaught-async.js:8:17)
at runCallback (timers.js:672:20)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)
(node:3900) There was an internal error in Node's debugger. Please report this bug.
kill EPERM
Error: kill EPERM
at exports._errnoException (util.js:1020:11)
at ChildProcess.kill (internal/child_process.js:409:26)
at Interface.killChild (_debugger.js:1631:16)
at process.Interface.process.on (_debugger.js:772:33)
at emitOne (events.js:101:20)
at process.emit (events.js:188:7)
at process.exit (internal/process.js:166:15)
at process.<anonymous> (_debugger.js:40:13)
at emitOne (events.js:96:13)
at process.emit (events.js:188:7)
events.js:160
throw er; // Unhandled 'error' event
^
Error: kill EPERM
at exports._errnoException (util.js:1020:11)
at ChildProcess.kill (internal/child_process.js:409:26)
at process.<anonymous> (_debugger.js:39:44)
at emitOne (events.js:96:13)
at process.emit (events.js:188:7)
at process._fatalException (bootstrap_node.js:300:26)Related: #18177
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
Activity
maclover7 commentedon Feb 5, 2018
cc @nodejs/platform-windows
Trott commentedon Oct 18, 2018
It seems like perhaps this should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that.