[Bug] Unit Test On windows-latest (JDK: 8) action failed about dubbo

[AlbumenJ]

Can you provide your workflow url? The msg above is not the root cause/

in this url. In general, the "Build and Test Scheduled 3.1" and "Build and Test Scheduled 3.3" workflows mostly result in errors, while the "Build and Test Scheduled 3.2" version occasionally succeeds.

I feel like you're talking about a normal error, not a unit test faild.I see you gave a few links 3.2 to find the end because of plugin issues.

I don't think it's a normal error. Version 3.2 might be, but versions 3.1 and 3.3 both report stable errors, which means there is indeed a problem with the code and it needs to be modified, rather than thinking it's a normal error.

Yep, you're right. But most of the failure are due to the stability of test cases. This is really hard and will takes lots of time to enhance.

[AlbumenJ]

Can you provide your workflow url? The msg above is not the root cause/

[sunheyi6]

Can you provide your workflow url? The msg above is not the root cause/

in this url.
In general, the "Build and Test Scheduled 3.1" and "Build and Test Scheduled 3.3" workflows mostly result in errors, while the "Build and Test Scheduled 3.2" version occasionally succeeds.

[wcy666103]

Can you provide your workflow url? The msg above is not the root cause/

in this url. In general, the "Build and Test Scheduled 3.1" and "Build and Test Scheduled 3.3" workflows mostly result in errors, while the "Build and Test Scheduled 3.2" version occasionally succeeds.

I feel like you're talking about a normal error, not a unit test faild.I see you gave a few links 3.2 to find the end because of plugin issues.

[sunheyi6]

Can you provide your workflow url? The msg above is not the root cause/

in this url. In general, the "Build and Test Scheduled 3.1" and "Build and Test Scheduled 3.3" workflows mostly result in errors, while the "Build and Test Scheduled 3.2" version occasionally succeeds.

I feel like you're talking about a normal error, not a unit test faild.I see you gave a few links 3.2 to find the end because of plugin issues.

I don't think it's a normal error. Version 3.2 might be, but versions 3.1 and 3.3 both report stable errors, which means there is indeed a problem with the code and it needs to be modified, rather than thinking it's a normal error.