Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WFLY-2641 - fix NPE that could occur intermittently #59

Closed
wants to merge 1 commit into from

Conversation

ctomc
Copy link

@ctomc ctomc commented Dec 18, 2013

With this fix WildFly testsuite is much more stable.

I know this fix is not proper solution, but until we have one, lets keep this.

I could track down that root cause has to do with Expected Exception handling but could not narrow it down where exactly should it be fixed.
It could as well be related to bug/change in junit 4.11 for more see junit-team/junit4#711

@@ -287,7 +287,7 @@ public Object getInstance()
return test;
}
});
if(result.getThrowable() != null)
if (result != null && result.getThrowable() != null)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just masking some type of error.. Can't add this and pretend the test passed..

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests still fails and we seem to get proper failure back

@aslakknutsen
Copy link
Member

Have you tried to downgrade to junit 4.10?

@ctomc
Copy link
Author

ctomc commented Dec 18, 2013

We tried downgrading to 4.10 but we have too much testsuite framework code written that uses 4.11 features.
I am doing some testing now with our custom build of 4.12 (4.11 + fixes for expected exceptions) will let you know how it goes. But initial testing was not too promising.

@ctomc
Copy link
Author

ctomc commented Jan 8, 2014

Can we get this merged & release with this fix in it?
Or should we do 1.12.WildFly release and use that in our WildFly until proper solution is found?

@aslakknutsen
Copy link
Member

Not the correct fix. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants