Closed pfgithub closed 2 hours ago
:x: @Jarred-Sumner, your commit 98b97727317cea01782eea9659d528b1c7747225 has 13 failures in #6629
:
test/js/bun/spawn/spawn-streaming-stdin.test.ts
- 1 failing on ๐ง 3.20 x64-baselinetest/package.json
- timeout on ๐ง 3.20 x64-baselinetest/integration/next-pages/test/dev-server.test.ts
- 1 failing on ๐ง 3.20 x64-baselinetest/integration/next-pages/test/dev-server.test.ts
- 1 failing on ๐ง 3.20 x64test/v8/v8.test.ts
- 22 failing on ๐ง 3.20 aarch64test/v8/v8.test.ts
- 22 failing on ๐ง 3.20 x64-baselinetest/v8/v8.test.ts
- 22 failing on ๐ง 3.20 x64test/js/node/child_process/child_process.test.ts
- 1 failing on ๐ง 3.20 aarch64test/js/node/child_process/child_process.test.ts
- 1 failing on ๐ง 3.20 x64-baselinetest/js/node/child_process/child_process.test.ts
- 1 failing on ๐ง 3.20 x64test/cli/install/bun-link.test.ts
- 4 failing on ๐ง 3.20 aarch64test/cli/install/bun-link.test.ts
- 4 failing on ๐ง 3.20 x64-baselinetest/cli/install/bun-link.test.ts
- 4 failing on ๐ง 3.20 x64test/js/node/fs/fs-promises-writeFile-async-iterator.test.ts
- 1 failing on ๐ง 22.04 aarch64test/cli/install/registry/bun-install-registry.test.ts
- timeout on ๐ง 22.04 x64test/cli/install/registry/bun-install-registry.test.ts
- timeout on ๐ง 3.20 x64test/js/web/timers/setTimeout.test.js
- 1 failing on ๐ง 22.04 x64test/js/bun/http/serve.test.ts
- segmentation fault on ๐ง 22.04 aarch64test/js/bun/http/serve.test.ts
- segmentation fault on ๐ง 3.20 aarch64test/js/bun/http/serve.test.ts
- segmentation fault on ๐ง 3.20 x64-baselinetest/js/bun/http/serve.test.ts
- segmentation fault on ๐ง 3.20 x64test/js/bun/http/serve.test.ts
- 1 failing on ๐ 14 aarch64test/js/bun/http/serve.test.ts
- 1 failing on ๐ 14 x64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 12 x64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 11 x64-baselinetest/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 12 x64-baselinetest/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 11 x64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 11 aarch64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 22.04 x64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 20.04 x64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 20.04 x64-baselinetest/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 20.04 aarch64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 3.20 aarch64test/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 3.20 x64-baselinetest/js/node/test/parallel/fs-watch-recursive-linux-parallel-remove.test.js
- 1 failing on ๐ง 3.20 x64test/integration/next-pages/test/next-build.test.ts
- 1 failing on ๐ง 22.04 x64test/js/web/websocket/websocket-client.test.ts
- 4 failing on ๐ช 2019 x64
What does this PR do?
Fixes #15314, Fixes #15326
I'm not sure why it used to work in 1.1.24 yet - "\uFFFF" may have passed through directly, but "\uFFFFยง" should have gone through the utf-16 path which had the same bug and yet it used to work