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

fix invalid assertion check in test #3188

Merged
merged 1 commit into from
Oct 11, 2018

Conversation

LinHu2016
Copy link
Contributor

- collection Usage of the same memoryPool might be different
between getCollectionUsage() calls.

Signed-off-by: Lin Hu linhu@ca.ibm.com

@pshipton pshipton requested a review from smlambert October 10, 2018 00:24
@@ -833,7 +833,8 @@ public void testMemoryPoolMXBeanProxy() {
MemoryUsage directUsage = realBean.getCollectionUsage();
validateMemoryUsage(proxyUsage);
validateMemoryUsage(directUsage);
AssertJUnit.assertEquals(directUsage, proxyUsage);
/* directUsage and proxyUsage could be different, if gc happened between getCollectionUsage() calls*/
// AssertJUnit.assertEquals(directUsage, proxyUsage);

Copy link
Contributor

Choose a reason for hiding this comment

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

Are you keeping it in the code as a comment to come back to it? If it is invalid, do you not simply want to remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed the assertion check and leave comment for a reminder

	- collection Usage of the same memoryPool might be different
	between getCollectionUsage() calls.

Signed-off-by: Lin Hu <linhu@ca.ibm.com>
@pshipton pshipton merged commit 3a665b7 into eclipse-openj9:master Oct 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants