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

Paul Noden updated SLING-425:
-----------------------------


Sorry, but the tests for all three rotate tests still failed.

I checked the contents of the log files and they seemed accurate, so I turned 
on the exception logging.

I commented out assertTrue(test.length() > 0); out in all three tests and tried 
again : failed
I additionally commented out assertTrue(test0.exists()); for the rotate 0 and 1 
tests and tried again : failed
I additionally commented out assertTrue(test1.exists()); for the rotate1 tests 
: success (same org.apache.sling.launchpad.webapp.integrationtest errors due to 
wait expired - talked to bertrand and may be raising a new jira for these, 
depending on some environment improvements i've made - which might lead to some 
hints and tips for building with maven )

> SlingLogFileWriter fails three test cases
> -----------------------------------------
>
>                 Key: SLING-425
>                 URL: https://issues.apache.org/jira/browse/SLING-425
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>         Environment: Windows
>            Reporter: Paul Noden
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: SlingLogFileWriterTest.java
>
>
> The test for SlingLogFileWriter failed in the three test cases in 
> SlingLogFileWriterTest where assertTrue(test.exists() && test.length() > 0) 
> is made. I took the liberty of commenting out from this line to the end of 
> each test case and found that all the other tests  in the build process on 
> windows still reported successful - with the exception of the tests run once 
> sling has started up, all of which fail  with "Sling services not 
> available."- I'm hoping this is a consequence of these logging issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to