> > That is caused by Java 25 as it is not yet on white list for vectorization > (we haven't checked if the incubator API of vectors is still compatible). I > just wonder why this happens at all, how comes that it initializes the > vectorization when executing this test? > I did look at the stack trace - seems like the test infrastructure (randomization) somehow triggers class loading. I didn't dig deeper since it's not really a crucial test - it just means to check whether we capture the output correctly (and we do).
Dawid
