[Bug]: 13.4.0 regression caused when process does not exist when running in Jest

[jimmydief]

Bug description

Similar to #8476, I can only reproduce this when killing Puppeteer as part of the teardown logic of my Jest tests. The stack trace looks like this:

kill ESRCH
  at pidExists (node_modules/puppeteer/src/node/BrowserRunner.ts:331:20)
  at BrowserRunner.kill (node_modules/puppeteer/src/node/BrowserRunner.ts:190:39)
  at node_modules/puppeteer/src/node/BrowserRunner.ts:177:14

I believe that this is likely only reproducible in Jest due to jestjs/jest#2549. Regardless, the instanceof Error check here seems unnecessary. Given that Puppeteer is likely widely used in Jest, fixing this here seems practical.

puppeteer/src/node/BrowserRunner.ts

Line 333 in 465a7c4

if (error instanceof Error) {

Puppeteer version

13.4.0

Node.js version

14.16.1

npm version

6.14.12

What operating system are you seeing the problem on?

macOS

Relevant log output

No response