You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2013/10/21 10:42:41 UTC

[jira] [Updated] (SLING-3194) failure running sling.extensions.event unit/integraiton tests on windows?

     [ https://issues.apache.org/jira/browse/SLING-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert updated SLING-3194:
----------------------------------

    Attachment: 131021_failsafe-reports.zip

the failures are different from time to time. sometimes only on IT fails, sometimes more than one, sometimes it runs without failure.

other example of a test run today - two failures
{noformat}
Results :

Tests in error:
  testHistory(org.apache.sling.event.it.HistoryTest): test timed out after 300000 milliseconds
  testOrderedQueue(org.apache.sling.event.it.OrderedQueueTest): test timed out after 300000 milliseconds

Tests run: 18, Failures: 0, Errors: 2, Skipped: 0
{noformat}
with detailed results in [^131021_failsafe-reports.zip]

> failure running sling.extensions.event unit/integraiton tests on windows?
> -------------------------------------------------------------------------
>
>                 Key: SLING-3194
>                 URL: https://issues.apache.org/jira/browse/SLING-3194
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Event 3.3.0
>         Environment: Win 7 64bit, JDK 1.7.0_17
>            Reporter: Stefan Seifert
>            Priority: Minor
>         Attachments: 131021_failsafe-reports.zip
>
>
> this is a follow up of this mail thread
> http://apache-sling.73963.n3.nabble.com/failure-running-sling-extensions-event-unit-integraiton-tests-on-windows-tt4027989.html#none
> with current revision in trunk (rev. 1533892) it is still happening - or happening again. the problem is that it sometimes work, most times does not work.
> last comment from carsten:
> {quote}
> I fixed one thing in the Classloading test which removes the started job
> from the history...this shouldn't have an impact though
> Could you please comment out line 222 in the Classloading test and retun
> the tests, so hopefully this gives us a clue about what is going on.
> Carsten 
> {quote}



--
This message was sent by Atlassian JIRA
(v6.1#6144)