Hi, Vikrant.
Thanks for the feedback, this failure was due to a bug in Mac, Component.getLocation() was giving an incorrect/inconsistent initial value when the component is located at (0,0). I have filed a bug for this issue: https://bugs.openjdk.java.net/browse/JDK-8201364 .
I have added a comment to this bug, please take a look. -- Best regards, Sergey.
