activitypods / activitypods/activitypods
Jest doesn't exit after tests completed
- 主要語言
- JavaScript
- 星號
- 260
- 分支
- 24
- PR 合併指標
- 30 天內沒有已合併 PR
描述
This happens for various tests even though:
```js
afterAll(async () => {
await podProvider.stop();
await appServer.stop();
});
```
are called.
Jest says: ``This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.`` Though when adding the flag, there is no additional information provided.
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
Start by locating the test suites where `afterAll` calls `podProvider.stop()` and `appServer.stop()`, then trace setup/teardown around those helpers. Check Jest config and any shared test bootstrap files for other long-running servers, DB clients, timers, or sockets that are not closed. Re-run the suite with `jest --detectOpenHandles` as the issue already suggests, then verify no extra handles remain. Issue is done when the suite exits normally and Jest no longer shows the async operations warning.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript
- 領域
- testing
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 半天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 50/100