-
-
Notifications
You must be signed in to change notification settings - Fork 29
Fix NAs behavior #1441
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 NAs behavior #1441
Conversation
|
@edelarua @ayogasekaram could you take a look? I am testing downstream |
Unit Tests Summary 1 files 85 suites 1m 39s ⏱️ Results for commit a7835f1. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 3da2c99 ♻️ This comment has been updated with latest results. |
edelarua
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Melkiades,
Just one suggestion from me. Otherwise it looks good!
Co-authored-by: Emily de la Rua <emily.de_la_rua@contractors.roche.com> Signed-off-by: Davide Garolini <dgarolini@gmail.com>
Code Coverage SummaryDiff against mainResults for commit: a7835f1 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
shajoezhu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for confirming it works well on the original case!
#1440
If this is unified correctly may have impacts downstream