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

[CodeStyle] use np.testing.assert_array_equal(...) instead of self.assertTrue(np.array_equal(...)) (part 3) #45251

Merged
merged 1 commit into from
Aug 19, 2022

Conversation

SigureMo
Copy link
Member

@SigureMo SigureMo commented Aug 18, 2022

@paddle-bot
Copy link

paddle-bot bot commented Aug 18, 2022

你的PR提交成功,感谢你对开源项目的贡献!
请关注后续CI自动化测试结果,详情请参考Paddle-CI手册
Your PR has been submitted. Thanks for your contribution!
Please wait for the result of CI firstly. See Paddle CI Manual for details.

@paddle-bot paddle-bot bot added contributor External developers status: proposed labels Aug 18, 2022
@luotao1 luotao1 merged commit 4e2a3c1 into PaddlePaddle:develop Aug 19, 2022
@luotao1 luotao1 changed the title [WIP][CodeStyle] use np.testing.assert_allclose instead of self.assertTrue(np.allclose(...)) (part 3) [CodeStyle] use np.testing.assert_allclose instead of self.assertTrue(np.allclose(...)) (part 3) Aug 19, 2022
@luotao1 luotao1 changed the title [CodeStyle] use np.testing.assert_allclose instead of self.assertTrue(np.allclose(...)) (part 3) [CodeStyle] use np.testing.assert_array_equal(...) instead of self.assertTrue(np.array_equal(...)) (part 3) Aug 19, 2022
@SigureMo SigureMo deleted the assert-allclose-part3 branch August 19, 2022 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributor External developers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Recommend to use np.testing.assert_allclose instead of assertTrue(np.allclose(...))
2 participants