[
https://issues.apache.org/jira/browse/SLING-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583961#comment-16583961
]
Bertrand Delacretaz commented on SLING-7832:
--------------------------------------------
Found the weirdness, the test uses the {{/content}} node and in my test setup
was bothered by pre-existing content there, and deleted that node after the
test, meaning that further tests ran fine.
The {{/content}} node is now moved aside and restored [1], which should fix
this issue.
Let's wait for the Jenkins results to confirm if we can mark this resolved.
[1]
https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/48c0e963b781974a6bf2613e97701f5571bc6953
> ResourceResolverProxyTest fails: write(param) is only valid in arrays
> ---------------------------------------------------------------------
>
> Key: SLING-7832
> URL: https://issues.apache.org/jira/browse/SLING-7832
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Reporter: Robert Munteanu
> Assignee: Bertrand Delacretaz
> Priority: Major
>
> This test consistently fails locally and on Jenkins:
> {noformat}javax.json.stream.JsonGenerationException: write(param) is only
> valid in arrays
> at
> org.apache.sling.launchpad.webapp.integrationtest.ResourceResolverProxyTest.runWriteableResourcesTest(ResourceResolverProxyTest.java:26){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
