You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally openjdk test DIAGNOSTIC level was set 'noDetails' to skip the test output due to parse failures of special characters, which results in no any failure testcases information in tap files. For jenkins jobs those failure information can be got from console output or junit plugin. We'd like to add the failed testcase name information in tap file, which can be clear and simple when regather the grinder's tap file by rerun failing tests using jdk_custom target.
The text was updated successfully, but these errors were encountered:
Originally openjdk test DIAGNOSTIC level was set 'noDetails' to skip the test output due to parse failures of special characters, which results in no any failure testcases information in tap files. For jenkins jobs those failure information can be got from console output or junit plugin. We'd like to add the failed testcase name information in tap file, which can be clear and simple when regather the grinder's tap file by rerun failing tests using jdk_custom target.
The text was updated successfully, but these errors were encountered: