[jira] [Commented] (SLING-5452) ClientSideTeleporter should check for web console readiness

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130099#comment-15130099 ] 

Bertrand Delacretaz commented on SLING-5452:
--------------------------------------------

As reported by [~rombert] the repoinit tests are currently failing on Jenkins and this is apparently the core issue:

{code}
java.io.IOException: Got status code 404 for http://localhost:49661/system/console/bundles
	at org.apache.sling.testing.teleporter.client.TeleporterHttpClient.installBundle(TeleporterHttpClient.java:77)
{code}

> ClientSideTeleporter should check for web console readiness
> -----------------------------------------------------------
>
>                 Key: SLING-5452
>                 URL: https://issues.apache.org/jira/browse/SLING-5452
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>
> Before installing its test bundle, the {{ClientSideTeleporter}} should (optionally?) check, via HTTP, that the OSGi console is ready to accept it. The customizer could optionally set a longer retry timeout for installing the bundle.
> This is not a problem in our launchpad test suite as the Sling readiness is checked extensively before starting tests, but in smaller test suites it's useful for the teleporter to be self-contained in this respect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)