Skip to content
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.

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

investigate flaky test-benchmark-child-process on Windows #12817

Closed
Trott opened this issue May 3, 2017 · 5 comments
Closed

investigate flaky test-benchmark-child-process on Windows #12817

Trott opened this issue May 3, 2017 · 5 comments
Labels
benchmark Issues and PRs related to the benchmark subsystem. child_process Issues and PRs related to the child_process subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.

Comments

@Trott
Copy link
Member

Trott commented May 3, 2017

  • Version: 8.0.0-pre
  • Platform: win2008r2
  • Subsystem: test

https://ci.nodejs.org/job/node-test-binary-windows/8189/RUN_SUBSET=3,VS_VERSION=vs2015-x86,label=win2008r2/console

not ok 356 sequential/test-benchmark-child-process
  ---
  duration_ms: 60.211
  severity: fail
  stack: |-
    timeout

refack adding
Ref: #12560

@Trott Trott added benchmark Issues and PRs related to the benchmark subsystem. child_process Issues and PRs related to the child_process subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform. labels May 3, 2017
@refack refack self-assigned this May 4, 2017
@refack
Copy link
Contributor

refack commented May 4, 2017

It's that [expletive] yes.exe again.

refack added a commit to refack/node that referenced this issue May 4, 2017
@refack refack closed this as completed in 68c933c May 6, 2017
@refack
Copy link
Contributor

refack commented May 6, 2017

anchnk pushed a commit to anchnk/node that referenced this issue May 19, 2017
PR-URL: nodejs#12821
Fixes: nodejs#12817
Refs: nodejs#12658
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@refack
Copy link
Contributor

refack commented Jun 4, 2017

Reopening:
https://ci.nodejs.org/job/node-test-binary-windows/8986/RUN_SUBSET=2,VS_VERSION=vs2015,label=win2012r2/

not ok 370 sequential/test-benchmark-child-process
  ---
  duration_ms: 0.623
  severity: fail
  stack: |-
    
    child_process\child-process-exec-stdout.js
    child_process\child-process-exec-stdout.js dur=0 len=1: 0
    ERROR: The process with PID 3816 (child process of PID 3692) could not be terminated.
    Reason: There is no running instance of the task.
    child_process.js:611
        throw err;
        ^
    
    Error: Command failed: taskkill /f /t /pid 3816
    ERROR: The process with PID 3816 (child process of PID 3692) could not be terminated.
    Reason: There is no running instance of the task.
    
    
        at checkExecSyncError (child_process.js:568:13)
        at Object.execSync (child_process.js:608:13)
        at Timeout._onTimeout (c:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vs2015\label\win2012r2\benchmark\child_process\child-process-exec-stdout.js:36:21)
        at ontimeout (timers.js:488:11)
        at tryOnTimeout (timers.js:323:5)
        at Timer.listOnTimeout (timers.js:283:5)
    assert.js:60
      throw new errors.AssertionError({
      ^
    
    AssertionError [ERR_ASSERTION]: 1 === 0
        at ChildProcess.child.on (c:\workspace\node-test-binary-windows\RUN_SUBSET\2\VS_VERSION\vs2015\label\win2012r2\test\sequential\test-benchmark-child-process.js:19:10)
        at emitTwo (events.js:125:13)
        at ChildProcess.emit (events.js:213:7)
        at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
  ...

@refack refack reopened this Jun 4, 2017
refack added a commit to refack/node that referenced this issue Jun 7, 2017
also some cleanup

PR-URL: nodejs#13457
Refs: nodejs#12817
Reviewed-By: Tobias Nießen <[email protected]>
@bzoz
Copy link
Contributor

bzoz commented Jun 9, 2017

@refack, did #13457 solve this?

@refack
Copy link
Contributor

refack commented Jun 9, 2017

@refack, did #13457 solve this?

I think so.


Fixed by #13457

@refack refack closed this as completed Jun 9, 2017
addaleax pushed a commit that referenced this issue Jun 10, 2017
also some cleanup

PR-URL: #13457
Refs: #12817
Reviewed-By: Tobias Nießen <[email protected]>
gibfahn pushed a commit that referenced this issue Jun 20, 2017
PR-URL: #12821
Fixes: #12817
Refs: #12658
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this issue Jul 11, 2017
PR-URL: #12821
Fixes: #12817
Refs: #12658
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@refack refack removed their assignment Oct 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Issues and PRs related to the benchmark subsystem. child_process Issues and PRs related to the child_process subsystem. test Issues and PRs related to the tests. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants