I took a quick peek at testJsonContentTypeException() in
PostServletOutputContentTypeTest and
it looks as if the test tries to invoke a "copy" operation by doing this
1. Create a node at
http://localhost:8080/launchpad-integration-tests/PostServletOutputContentTypeTest/<X>/abs/<Y>/dest
where <X> and <Y> are timestamps
2. Post a "copy" :operation to
http://localhost:8080//launchpad-integration-tests/PostServletOutputContentTypeTest/<X>
where the :dest is
/launchpad-integration-tests/PostServletOutputContentTypeTest/<X>/abs/<Y>/dest/
This leads to a recursive invocation of copy(Node src, Node dstParent,
String name)
in org.apache.sling.servlets.post.impl.operations.CopyOperation that
will eventually
fail due to a java.lang.StackOverflowError. On my Linux setup this can
take quite
some time before it actually fails.
/Pontus
On 2011-04-07 00:25, Pontus Amberg wrote:
Ok. I'll see if I can get some time to look at it during the weekend.
/Pontus
On 2011-04-05 15:30, Bertrand Delacretaz wrote:
Hi,
On Tue, Apr 5, 2011 at 2:30 AM, Pontus
Amberg<pontus.amb...@comhem.se> wrote:
I've just tried to build the current trunk and noticed that
testJsonContentTypeException() in
PostServletOutputContentTypeTest took 31 minutes to complete! All
the other
test in
PostServletOutputContentTypeTest worked as normal....
I haven't seen that (or not that long at least), could you check the
http traffic during this test?
The test follows redirects, maybe there's something wrong there.
-Bertrand
