Frederic, could you figure out how to resolve 8231031: runtime/ReservedStack/ReservedStackTest.java fails after jsr166 refresh https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/ReservedStackTest/index.html https://bugs.openjdk.java.net/browse/JDK-8231031
On Mon, Sep 23, 2019 at 11:08 PM David Holmes <david.hol...@oracle.com> wrote: > Except when I run it through our test system ReservedStackTest is still > failing :( > > I tested it initially when Fred proposed it and that went fine. It also > passes for me locally on Linux. > > David > > On 24/09/2019 12:20 pm, David Holmes wrote: > > Hi Martin, > > > > That all seems fine to me. > > > > Thanks, > > David > > > > On 24/09/2019 3:43 am, Martin Buchholz wrote: > >> We now have a fix-up integration that removes all the previously > >> excluded tests from their exclude lists. > >> > >> > https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/overview.html > >> > >> > >> 8231031: runtime/ReservedStack/ReservedStackTest.java fails after > >> jsr166 refresh > >> > https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/ReservedStackTest/index.html > >> > >> https://bugs.openjdk.java.net/browse/JDK-8231031 > >> > >> LockInfo objects now restored to their previous values (although David > >> was looking at future improvements). > >> > >> 8231032: ThreadMXBean locking tests fail after JSR 166 refresh > >> > https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/wrong-blocker/index.html > >> > >> https://bugs.openjdk.java.net/browse/JDK-8231032 > >> > >> 8231036: vmTestbase monitoring tests fail after JSR 166 refresh > >> > https://cr.openjdk.java.net/~martin/webrevs/jdk/jsr166-integration/SynchronizerLockingThreads/index.html > >> > >> https://bugs.openjdk.java.net/browse/JDK-8231036 >
