Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_UNHANDLED_REJECTION wrongly reported in node 18 when running junit test. #49507

Open
zybjcdl opened this issue Sep 6, 2023 · 4 comments
Open
Labels
stalled Issues and PRs that are stalled.

Comments

@zybjcdl
Copy link

zybjcdl commented Sep 6, 2023

Version

v18.17.1

Platform

Darwin 192.168.1.112 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000 arm64

Subsystem

No response

What steps will reproduce the bug?

I have several junit test cases , I have upgraded to Node 18.17.1 , and always the third case will fail with following error:
image
For example we have testfile1 testfile2 testfile3, the first 2 files passed, the third fail.
If I copy the same content from testfile2 to testfile3, still, the third will fail.
So I don't think it is our test cases issue.
All the things works well when we using node 14.
There is no promise used in all the testfiles.

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?

The test cases always fail in the third case.
Report : ERR_UNHANDLED_REJECTION

Additional information

No response

@zybjcdl
Copy link
Author

zybjcdl commented Sep 6, 2023

If I run it one by one, I even see this, all the test are successfully, but finally it still report:
image

@aduh95
Copy link
Contributor

aduh95 commented Sep 6, 2023

Do you have a repro (that do not involve downloading code from the internet)? Without a repro, it's very hard to debug and it's unlikely you'll find someone to work on it.

@RedYetiDev RedYetiDev added the stalled Issues and PRs that are stalled. label Aug 10, 2024
Copy link
Contributor

This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open.

@RedYetiDev
Copy link
Member

Hi! This issue has been waiting for more information for around a year, and without new information, it's unlikely action will be taken. For that reason, I've marked this PR as stalled, but feel free to undo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stalled Issues and PRs that are stalled.
Projects
None yet
Development

No branches or pull requests

3 participants