Hi Rory, Now it is accessed. But the issue JDK-8168389 has resolution=‘Cannot Reproduce’ for now, before it was ‘Duplicate’ Is that correct?
Thanks, Vitaly > On 21 Dec 2016, at 21:10, Rory O'Donnell <rory.odonn...@oracle.com> wrote: > > Hi Vitaly, > > You should be able to view the bug now, I am still looking into it. > Rgds,Rory > > On 21/12/2016 10:26, Vitaly Provodin wrote: >> Ooops. I do not have an access to JDK-8072110 - Bug System requires me to >> log in (but I do not have an account yet) >> Does the issue JDK-8072110 have some restrictions? >> >>> On 21 Dec 2016, at 17:21, Rory O'Donnell <rory.odonn...@oracle.com >>> <mailto:rory.odonn...@oracle.com>> wrote: >>> >>> Hi Vitaly, >>> >>> I will look into this, the duplicate bug is JDK-8072110 - which was closed >>> as "will not fix". >>> >>> I will look into this further, but at this time of year it may take some >>> time. >>> >>> Rgds,Rory >>> >>> On 21/12/2016 04:25, Vitaly Provodin wrote: >>>> Good time of day >>>> >>>> Recently I detected that the issue >>>> https://bugs.openjdk.java.net/browse/JDK-8168389 >>>> <https://bugs.openjdk.java.net/browse/JDK-8168389> was closed as duplicate >>>> but there are no information about original bug. >>>> Could you pleas provide information about what bug was duplicated by >>>> JDK-8168389 <https://bugs.openjdk.java.net/browse/JDK-8168389>? >>>> >>>> Thanks, >>>> Vitaly >>> >>> -- >>> Rgds,Rory O'Donnell >>> Quality Engineering Manager >>> Oracle EMEA , Dublin, Ireland >> > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland
