Closed Bug 1644826 Opened 4 years ago Closed 1 year ago

Keyboard interrupt on ./mach puppeteer-test doesn't kill all child processes

Categories

(Remote Protocol :: Agent, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: impossibus, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression, Whiteboard: [puppeteer-beta2-mvp])

STR: run ./mach puppeteer-test then hit ^C (twice)
Result: the npm process is killed but not the child node process (mocha) nor the child Firefox process(es)

Is that a new regression from that sync and it didn't happen before? I always faced problems with using Ctrl+C for interrupting the Puppeteer unit tests.

I think it's a regression due to how mocha is called. Ctrl+C worked better for me before the sync.

Puppeteer 4.0.0 fixed it. So we may want to just downstream sync again?

https://github.com/puppeteer/puppeteer/pull/6011

Flags: needinfo?(mjzffr)

yep

Flags: needinfo?(mjzffr)

I filed bug 1647439 for the 4.0.0 downstream sync.

Depends on: 1647439

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #3)

Puppeteer 4.0.0 fixed it. So we may want to just downstream sync again?

https://github.com/puppeteer/puppeteer/pull/6011

The problem is the same with 4.1, both with Firefox and Chrome, so I still think it's due to how mach launches mocha.

No longer depends on: 1647439
Severity: -- → S3

As noticed today this behavior results in a terrible user experience. Whenever I hit Ctrl+C to abort a puppeteer unit test job via mach the mocha node.js job spawns itself over and over again. I was not able to find a way to actually kill the process, and was forced to close x-amount of firefox processes until all the tests have been processed.

We should get this fixed as part of beta2 to allow us to run local puppeteer tests without issues.

Priority: P3 → P2
Whiteboard: [puppeteer-beta2-mvp]

This is no longer a problem.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.