Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-7659

Add random to working directory path to support unclean builds

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Done
    • Testing PaxExam 2.0.0
    • Testing PaxExam 3.0.0
    • Testing
    • None

    Description

      Test using o.a.s.testing.paxexam block if run without "mvn clean"

      This happens for (at least) the following modules:

      • sling-org-apache-sling-commons-html which uses o.a.s.testing.paxexam 2.0.0
      • sling-org-apache-sling-resource-presence which uses o.a.s.testing.paxexam 0.0.4

      The integration tests work fine with mvn clean install but running mvn install right after that causes the tests to hang and time out (after approximately 6 minutes).

      Deleting target/paxexam folder before running mvn install fixes the issue, so it's linked to existing OSGi state apparently.

      I'll attach a testing.log, I don't see any obvious clues in it but the tests block after this line:

      2018-05-09 11:59:56,003 DEBUG [BundleWatcher: 1] o.o.p.e.r.e.i.Probe 
      [Parser.java : 64] Registering Service: org.ops4j.pax.exam.ProbeInvoker 
      with Probe-Signature="PaxExam-d4e46627-3b02-462a-aa46-883ce54e3f9f" 
      and expression=
      "org.apache.sling.commons.html.it.TagsoupHtmlParserIT;testFeaturesConfiguration"
      

      Attachments

        1. testing.log
          12 kB
          Bertrand Delacretaz

        Activity

          People

            olli Oliver Lietz
            bdelacretaz Bertrand Delacretaz
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: