Skip to content

Resolve UnhandledRejectionWarning in e2e tests. #276

@HoOngEe

Description

@HoOngEe

Some e2e tests are emitting UnhandledPromiseRejectionWarning. Let's find out the reason and resolve the problems.

ChangeParams
    ✓ change (38ms)
(node:13789) UnhandledPromiseRejectionWarning: Error: CodeChain(3) process state is invalid: {
    "state": "stopping"
}
    at CodeChain.get testFramework [as testFramework] (/home/spkim2/foundry/test/src/helper/spawn.ts:100:19)
    at CodeChain.createPayTx (/home/spkim2/foundry/test/src/helper/spawn.ts:547:21)
    at CodeChain.sendPayTx (/home/spkim2/foundry/test/src/helper/spawn.ts:572:25)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:13789) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:13789) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions