<AWT Dev> [8] Review request for JDK-8029447 [TEST_BUG] AWT toolkit initialization fails with UnsatisfiedLinkError on linux x64
Alexander Zvegintsev
alexander.zvegintsev at oracle.com
Tue Dec 3 07:04:15 PST 2013
Hi Anthony,
As you can see in this issue history it was resolved as not an issue
firstly.
I am not a fan this changes too, however, it was supposed by Sergey and
Victor to fix these tests since the fix looks safe for now.
I'd actually prefer to not change these tests too.
Sergey, Victor, what do you think?
--
Thanks,
Alexander.
On 12/03/2013 06:35 PM, Anthony Petrov wrote:
> Hi Alexander,
>
> On the one hand, I agree that the nature of the tests is headless, and
> thus running them in this mode looks appropriate in general.
>
> On the other hand, I see that the root cause of the tests failure is a
> misconfigured PC on which the tests are being run. This issue can bite
> us (or rather, the tester) later on. Besides, the app-context related
> code may (in theory and/or in the future) behave differently in the
> headfull vs. headless mode, and this latter issue will in fact bite us.
>
> So, if you really-really want to fix this for JDK 8 now, you may
> consider this fix reviewed. However, I'd prefer to fix the PC's
> configuration instead of pushing this patch, or at least file a
> separate issue so that the configuration could be fixed later.
>
> --
> best regards,
> Anthony
>
> On 12/03/2013 06:12 PM, Alexander Zvegintsev wrote:
>> Hello, AWT Team.
>>
>> Please review the fix
>> http://cr.openjdk.java.net/~azvegint/jdk/8/8029447/webrev.00/
>> for the issue
>> https://bugs.openjdk.java.net/browse/JDK-8029447/
>>
>> These tests fail due to test execution was performed with 32-bit JDK on
>> a 64-bit Linux,
>> obviously this 64-bit Linux system doesn't have 32-bit libraries
>> installed. However,
>> test failure can be avoided by running these tests in headless mode.
>>
More information about the awt-dev
mailing list