Hi everyone, people have run into several test failures, here's a summary to make it easier to follow:
1. Some tests can be very slow with certain random parameters, and this can cause the smoke tester to take several hours -- this seems like a test-only problem, and we're working to address it in https://issues.apache.org/jira/browse/LUCENE-10473. 2. TestMatchAllDocsQuery#testEarlyTermination can fail with assertion -- this is a test-only issue, and has already been fixed in https://issues.apache.org/jira/browse/LUCENE-10472. 3. TestIndexWriterMergePolicy#testStressUpdateSameDocumentWithMergeOnGetReader can OOM -- this is a known issue and is not expected to occur outside of tests (https://issues.apache.org/jira/browse/LUCENE-10088) 4. *Security manager issues from Amazon's log4shell patch* -- not sure this requires a change on our end? It sounds like Mike is investigating the issues now (thanks!) 5. *Test suite may also stall on some machines? *-- Uwe mentioned "Looks like a problem with the test or some wrong assumption or some missing synchronized block (the Policeman Jenkins machine has many cores, so issues with not synchronized cache lines can happen easily)." Is this a different problem from #1 where we just have slow tests? I'm not sure if this is something we want to investigate as part of the release or if we think it can wait. Thanks, Julie On Fri, Mar 18, 2022 at 12:17 PM Michael Sokolov <[email protected]> wrote: > We had to do a workaround in our internal test suites by setting a > system property to trick this thing into not running; Maybe we can > apply that also here... > > On Fri, Mar 18, 2022 at 3:12 PM Dawid Weiss <[email protected]> wrote: > > > > I think this is Amazon trying to cope with log4shell - they've added > > external instrumentation. > > > > On Fri, Mar 18, 2022 at 7:51 PM Robert Muir <[email protected]> wrote: > > > > > > >> 2> at > java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > > > >> 2> at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71) > > > >> 2> at Log4jHotPatch.agentmain(Log4jHotPatch.java:93) > > > >> 2> ... 6 more > > > > > > > > > > > > Does anyone have an idea? > > > > > > > > > > Your JVM is broken, look at this Log4jHotPatch stuff causing trouble. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
