On Tue, 25 Jun 2024 17:45:23 GMT, Andrew John Hughes wrote:
> Is there still going to be some monitoring of these tests? Making it harder
> to run these tests potentially means that genuine failures can go unnoticed
> and JDK certificates are not updated when needed.
Tracking won’t be any diff
On Fri, 21 Jun 2024 16:11:34 GMT, Rajan Halade wrote:
>> Updated all the tests that depend on external infrastructure services as
>> manual. These tests may fail with external reasons, for instance - change in
>> CA test portal, certificate status updates, or network issues.
>
> Rajan Halade ha
On Fri, 21 Jun 2024 16:11:34 GMT, Rajan Halade wrote:
>> Updated all the tests that depend on external infrastructure services as
>> manual. These tests may fail with external reasons, for instance - change in
>> CA test portal, certificate status updates, or network issues.
>
> Rajan Halade ha
On Fri, 21 Jun 2024 13:10:00 GMT, Christoph Langer wrote:
>> Rajan Halade has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> fix typos
>
> test/jdk/security/infra/java/security/cert/CertPathValidator/certification/CAInterop.java
> line 30:
> Updated all the tests that depend on external infrastructure services as
> manual. These tests may fail with external reasons, for instance - change in
> CA test portal, certificate status updates, or network issues.
Rajan Halade has updated the pull request incrementally with one additional
On Thu, 20 Jun 2024 18:35:00 GMT, Rajan Halade wrote:
> Updated all the tests that depend on external infrastructure services as
> manual. These tests may fail with external reasons, for instance - change in
> CA test portal, certificate status updates, or network issues.
Looks good, although
