[jboss-jira] [JBoss JIRA] (WFLY-2893) Determine cause of unreported test failures

Tomaz Cerar (JIRA) issues at jboss.org
Fri Jan 9 09:51:30 EST 2015


     [ https://issues.jboss.org/browse/WFLY-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar resolved WFLY-2893.
-------------------------------
    Resolution: Done


This hasn't happened since, i did add few more safeguards just to make sure this doesn't happen again.

> Determine cause of unreported test failures
> -------------------------------------------
>
>                 Key: WFLY-2893
>                 URL: https://issues.jboss.org/browse/WFLY-2893
>             Project: WildFly
>          Issue Type: Task
>          Components: Build System, Test Suite
>    Affects Versions: 8.0.0.CR1
>            Reporter: Brian Stansberry
>            Assignee: Tomaz Cerar
>             Fix For: 9.0.0.Beta1
>
>
> Identify the reason why the failing tests that needed https://github.com/wildfly/wildfly/commit/90643bc435a9ba439cf2988e5b7407d1d48fb040 to get working did not fail the build. Those tests were failing for 2.5 months. Fortunately it was just a test problem, not a broken feature.
> They involved separate surefire executions. We want to avoid those, but sometimes they are needed to use different config files. We have separate executions in testsuite/integration/basic as well, covering a much broader scope, so if this kind of problem happened there as well we could have a big problem.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list