I found a way to disable the log4shell patch on my work machine, and got a pass:
SUCCESS! [1:00:57.577806]
I don't think we need to be concerned about trying to adapt to this
thing. It only conflicts with the test framework, and devs can turn it
off to run tests. Somehow our automated builds
Hi Julie, thanks for summarizing the issues, for 4, as far as I understand,
there's nothing that needs to be changed on lucece's end. We're still
having trouble running the smoke test on Amazon's machine, but I've tried
it on my own machine and it passed.
So here's my +1. SUCCESS!
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
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 wrote:
>
> I think this is Amazon trying to cope with log4shell - they've added
> external
Yeah this is endemic in our world now. I am having the same issue
On Fri, Mar 18, 2022 at 2:51 PM Robert Muir wrote:
>
> >> 2>at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> >> 2>at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71)
> >> 2>at
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 wrote:
>
> >> 2>at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> >> 2>at Log4jHotPatch.asmVersion(Log4jHotPatch.java:71)
> >>
>> 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
Hi
I tried to run the smoke test command on an EC2 instance, and I got several
failures like the one below:
Exception in thread "Attach Listener" Agent failed to start!
>
> org.apache.lucene.index.Test2BPostings > classMethod FAILED
> java.lang.AssertionError: The test or suite printed 48646
+1
SUCCESS! [1:08:44.248804]
On Thu, Mar 17, 2022 at 11:08 PM Uwe Schindler wrote:
> Hi,
>
>
>
> the test also failed several times in usual Jenkins jobs (see builds@lao
> list). Looks like a problem with the test or some wrong assumption or some
> missing synchronized block (the Policeman
