rsnext/test/production/standalone-mode
Hendrik Liebau 7523f327e0
Ensure required-server-files test can exit cleanly (#66765)
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.
2024-07-02 00:05:28 +02:00
..
basic Replace createNextDescribe with nextTestSetup (#64817) 2024-04-25 12:06:12 -06:00
ipv6 Redesign nextjs logging (#54713) 2023-09-05 11:40:00 +00:00
no-app-routes Replace createNextDescribe with nextTestSetup (#64817) 2024-04-25 12:06:12 -06:00
optimizecss Stop using baseUrl in root tsconfig (#64117) 2024-04-09 00:25:43 +02:00
required-server-files Ensure required-server-files test can exit cleanly (#66765) 2024-07-02 00:05:28 +02:00
response-cache Stop using baseUrl in root tsconfig (#64117) 2024-04-09 00:25:43 +02:00
type-module Stop using baseUrl in root tsconfig (#64117) 2024-04-09 00:25:43 +02:00