On Fri, 23 Oct 2020 14:33:11 GMT, Maurizio Cimadamore <mcimadam...@openjdk.org> wrote:
>> I'm not sure I get as to why the test fails on 32 bits - in the sense that >> it does not seem to rely on platform specific assumptions (at least on a >> quick look). On top of my head I'm not aware of what might have caused this >> to start working again in JDK-8254162, so maybe some more investigation is >> required? >> >> At the very least we should only disable the problematic spliterator test, >> which is, I believe "testSegmentSpliterator" - and leave the other running, >> which is useful, as this is an important stress test for spliterators. > > Ok - I understand at least why JDK-8254162 fixed it - JDK-8254162 uses a new > API to access memory (MemoryAccess) which disables alignment checks, so > that's why the issue doesn't happen. But that means that there could be a > latent issue in the test. Looking deeper. Thing is, I don't think there is a way to problem list the _TestNG_ testcase, is it? There is only a way to problem list the entire jtreg test or its separate `@run` with ID. Which is what the patch does. I would think that `generic-i586` only touches `x86_32`, and thus the test, while disabled there, is still operational on every other platform. I would love if there is was pointed fix that resolves the actual issue, though. ------------- PR: https://git.openjdk.java.net/jdk/pull/836
