On Fri, 3 Jun 2022 05:30:10 GMT, Sergey Bylokhov <s...@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 pull request has now been integrated. Changeset: a277590c Author: Sergey Bylokhov <s...@openjdk.org> URL: https://git.openjdk.java.net/jdk/commit/a277590c89b173fd9bc028c715564f18fe62f722 Stats: 28 lines in 2 files changed: 5 ins; 5 del; 18 mod 8287761: Make the logging of J2DBench stable Reviewed-by: aghaisas, prr ------------- PR: https://git.openjdk.java.net/jdk/pull/9008
