The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Provide 100% java code coverage for public Vector API
Comments
jcov issues have been fixed and code coverage for Vector API has been gathered successfully.
The results show public Vector API cc is 99%.
The 2 uncovered methods methods are:
1) jdk.incubator.vector.VectorOperators.$Conversion.ofReinterpret
2) jdk.incubator.vector.VectorSpecies.elementSize
Paul ([~psandoz] confirmed that
"Both those small methods call internal methods that are covered by other usages, so the risk is minimal".
Taking into account the uncovered methods are low risk and jdk16 schedule is quite tight
SQE is ok to give a waiver for jdk16 and postpone developing new tests to jdk17.
01-02-2021
Latest code coverage results for public Vector API show 99% of public API is covered.
Unfortunately these results are not gathered using latest promoted jdk16 build because
there are some jcov issues with latest jdk16/jdk17 build.
However I am pretty much sure there were no changes in Vector API which could change cc results.
Anyway, I will try to figure out jcov issue and get results for latest jdk16.
15-01-2021
[~epavlova], we are past rdp1, has 100% public API coverage been achieved?
04-01-2021
It was agreed with Dev team that 100% public API cc will be achieved after integration
of Vector API into jdk16 but before RDP1 of jdk16.