-
Notifications
You must be signed in to change notification settings - Fork 498
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
[TESTBUG][CI]runtime/coroutine/c1AssertFailTest.sh健壮性不够导致用例随机失败 #605
Comments
jia-wei-tang
added a commit
to jia-wei-tang/dragonwell8
that referenced
this issue
Dec 11, 2023
Summary: Determine the java mode before run normal logics. If java is release or fastdebug, just go to the ending early. Testing: hotspot/test/runtime/coroutine/c1AssertFailTest.sh Reviwers: lingjun-cg, yulei Issue: dragonwell-project#605
jia-wei-tang
added a commit
to jia-wei-tang/dragonwell8
that referenced
this issue
Dec 11, 2023
Summary: Determine the java mode before run normal logics. If java is release or fastdebug, just go to the ending early. Testing: hotspot/test/runtime/coroutine/c1AssertFailTest.sh Reviewrs: lingjun-cg, yulei Issue: dragonwell-project#605
jia-wei-tang
added a commit
to jia-wei-tang/dragonwell8
that referenced
this issue
Dec 11, 2023
Summary: Determine the java mode before run normal logics. If java is release or fastdebug, just go to the ending early. Testing: hotspot/test/runtime/coroutine/c1AssertFailTest.sh Reviewers: lingjun-cg, yulei Issue: dragonwell-project#605
jia-wei-tang
added a commit
that referenced
this issue
Dec 11, 2023
Summary: Determine the java mode before run normal logics. If java is release or fastdebug, just go to the ending early. Testing: hotspot/test/runtime/coroutine/c1AssertFailTest.sh Reviewers: lingjun-cg, yulei Issue: #605
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
测试job:https://github.com/dragonwell-project/dragonwell8/actions/runs/7139838371/job/19444520828?pr=604
如下图所示,启动java进程并放后台运行,用例预期每次该java进程运行超过2s再退出。而实际情况是,并不能保证该java进程在任意测试环境上,每次都能启动超过2s
修改建议:
1、在shell脚本加上set -x命令,增加调试信息,方便用例失败时根据调试信息确认用例失败原因
2、java命令之前加上time前缀,用例失败时可以得到java命令具体的执行时间
3、根据用例的测试意图,修改为更为健壮的方式,而不是通过sleep 2的方式
测试job截图:
The text was updated successfully, but these errors were encountered: