Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-18818

Test timeout in org.jboss.tools.jsf.verification.test

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 4.2.1.CR1
    • Fix Version/s: 4.12.0.Final
    • Component/s: jsf
    • Labels:
      None

      Description

      Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests.

      [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/buildTimeTrend

      But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1].

      [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow_4.2.luna/

      Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work.

      If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jeffmaury Jeff MAURY
              Reporter:
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: