-
Notifications
You must be signed in to change notification settings - Fork 494
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
Removing flaky by running the test only on RGB #1134
Conversation
Testing RGB gets 1.0 values too often which makes the test fail regularly. The same functionality is achieved by running only RGB in this test.
Looks like this is asserting that no pixel Your hypothesis is that depth (as a single channel) is more likely than RGB (with 3 channels) to trigger the test failure stochastically? CI still seems to fail here and this assertion seems doomed to fail stochastically anyway. Maybe better to check global image similarity instead of per-pixel similarity, right? See this sim test. |
Sorry, sorry. I got confused with my if statement. I was actually putting depth only in the test rather than rgb only. It should be fixed in this commit. I agree that there is still some stochasticity with RGB only BUT much much less. I have the test running in a while True loop and it has not failed yet. |
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.
Thank you for fixing the test. That makes sense to run the test only for one type of modalities.
Can you elaborate more on "Testing RGB gets 1.0 values too often" ?
Which values do you mean and how RGB contributes to failures?
Sorry, I meant depth. It seems that the max depth of 1 is happening very often. |
* Removing flaky by running the test only on RGB Testing RGB gets 1.0 values too often which makes the test fail regularly. The same functionality is achieved by running only RGB in this test. * wrong condition fix --------- Co-authored-by: vincentpierre <vincentpierre@users.noreply.github.com>
* Removing flaky by running the test only on RGB Testing RGB gets 1.0 values too often which makes the test fail regularly. The same functionality is achieved by running only RGB in this test. * wrong condition fix --------- Co-authored-by: vincentpierre <vincentpierre@users.noreply.github.com>
Testing depth gets 1.0 values too often which makes the test fail regularly. The same functionality is achieved by running only RGB in this test.
Motivation and Context
How Has This Been Tested
Types of changes
Checklist