How about the tests are changed to require a sys prop. That way you don't need a
On Jan 31, 2017, at 9:07 AM, Jason T. Greene
I agree with this approach but we need a way to group these failures in such a way that
we know whether or not a change has regressions.
> On Jan 31, 2017, at 9:03 AM, Kabir Khan <kabir.khan(a)jboss.com> wrote:
> The new invocation library, which is the basis of for the ejb client etc. is
currently developed in a branch. There are still about 130-140 test failures, but the team
feels it is time to merge to wildfly master at some stage later this week. This will get
more visibility of the failures and also lower the barrier of entry for whoever can jump
in and help fix the failures.
> Are there any objections to merging this?
>> From my point of view we would need to @Ignore the failing tests since there are
enough transient failures in our testsuite to make it hard to find usual suspects if the
number of failed tests is large. We could set up another CI job against a branch which is
master with the @Ignores reverted, and I could keep that up to date as I merge to master,
so that we get a good picture of the current testsuite failures.
> wildfly-dev mailing list
wildfly-dev mailing list