7523f327e0
When running `pnpm test-start test/production/standalone-mode/required-server-files/required-server-files.test.ts` locally, Jest hangs and prevents the process from exiting. In the CI, the issue is masked because `run-tests.js` uses `--forceExit`. The reason for the hanging process is that there are two server instances started, and only the last one is killed. By starting and killing the server for each test we can not only fix this, but also prevent the `should run middleware correctly (without minimalMode, with wasm)` test from affecting the other tests when flipping the `minimalMode` flag in `server.js`. I also reverted the darwin-specific overwrites of `appPort` that were added in #65722 and #66724. I don't think those are needed because after #65722 was created we did land #66285 which sets the hostname to be compatible with ipv4 and ipv6. If there's still a need to keep this then let me know, and I will restore it. |
||
---|---|---|
.. | ||
.stats-app | ||
development | ||
e2e | ||
examples | ||
integration | ||
lib | ||
production | ||
unit | ||
.gitignore | ||
build-turbopack-build-tests-manifest.js | ||
build-turbopack-dev-tests-manifest.js | ||
build-turbopack-tests-manifest.d.ts | ||
deploy-tests-manifest.json | ||
get-test-filter.js | ||
jest-setup-after-env.ts | ||
ppr-tests-manifest.json | ||
readme.md | ||
related-tests-manifest.json | ||
test-file.txt | ||
turbopack-build-tests-manifest.json | ||
turbopack-dev-examples-manifest.json | ||
turbopack-dev-tests-manifest.json |