Incosistant result between test and it in node:test

[himself65]

Version

v18.15.0

Platform

Darwin Himself65-Air 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:43 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T8112 arm64

Subsystem

test

What steps will reproduce the bug?

I will add a minimum repo to reproduce the bug later, but for now you have to clone and run it manually

https://github.com/toeverything/AFFiNE/tree/master/apps/server

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

Feishu20230628-161112.mp4

Additional information

No response

[aduh95]

Can you share code and copy/paste output rather than a video? Videos take more bandwidth and are not very helpful for folks with visual disabilities.

[atlowChemi]

I believe this has been fixed on newer Node versions: #46889

[cjihrig]

I agree it looks like it should be fixed. It looks like that change was backported in the 18.16.0 release, but this bug report is for 18.16.0.

EDIT: Looking at the backport commit I see that the added doc metadata says 18.6.0 instead of 18.16.0, so it's possible something went wrong.

[himself65]

Can you share code and copy/paste output rather than a video? Videos take more bandwidth and are not very helpful for folks with visual disabilities.

This is copy video from my colleague, and I confirm that he's node.js 18.15.0. And I double-checked that it works well in 18.16.0.

And the way to reproduce it is to replace it with test (code https://github.com/toeverything/AFFiNE/blob/2c95bfcc3dfe0dfbeee39254f80a6f4760fb67b8/apps/server/src/tests/workspace.spec.ts#L2)

Since I also believe it has been fixed. I won't give the minimum reproduction code.

[himself65]

I agree it looks like it should be fixed. It looks like that change was backported in the 18.16.0 release, but this bug report is for 18.16.0.

EDIT: Looking at the backport commit I see that the added doc metadata says 18.6.0 instead of 18.16.0, so it's possible something went wrong.

I think it's correct. because it did land in 18.6.0 first (#43420). My issue typed wrong version