RFR: 8287761: Make the logging of J2DBench stable

Ajit Ghaisas aghaisas at openjdk.java.net
Fri Jun 3 11:54:27 UTC 2022


On Fri, 3 Jun 2022 05:30:10 GMT, Sergey Bylokhov <serb at openjdk.org> wrote:

> Currently, the logging of the J2DBench differs from run to run. Each time the order of the parameters is random.
> 
> For example:
> First run: `with to Default Frame, bounce, 1x1, SrcOver, ident, !extraalpha, !xormode, !clip, Default, from transvolimg translucent, !touchsrc, Nearest neighbor`
> Next run: `with SrcOver, bounce, Nearest neighbor, ident, !touchsrc, to CompatImage(Opaque), Default, 1x1, !xormode, !clip, from bmcompatimg bitmask, !extraalpha
> `
> The root cause is that the options are stored in the Hashtable and printed in the "random" order. 
> 
> The fix replaces the usage of Hashtable by the LinkedHashMap. The code is tested on jdk1.7 and -source/-target 1.4

This is a good fix.

-------------

Marked as reviewed by aghaisas (Committer).

PR: https://git.openjdk.java.net/jdk/pull/9008



More information about the client-libs-dev mailing list