-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
autotest: large outliers in sub terrain test have low sq #27684
autotest: large outliers in sub terrain test have low sq #27684
Conversation
@ptrmu Please take a look |
Just a note. No test failures are acceptable - the test must be 100% (as-designed ;-) ), even in the face of adding random noise. People seem to have this thing against flapping tests :-) |
@peterbarker got it! I pushed another commit (I'll squash later), this should eliminate all test failures:
|
c99717d
to
b86871a
Compare
Looks great! |
b86871a
to
e28e0a3
Compare
e28e0a3
to
9b4157c
Compare
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.
Anything which reduces false positives is good in my book :-)
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.
Looks good!
Merged, thanks! |
The current test.Sub.SimTerrainSurftrak noise configuration is causing
moretest failuresthan we'd like.This PR adds
outlier_good_sq_limit
to the configuration. If the error exceedsoutlier_good_sq_limit
then the signal quality drops from 100 (best) to 50 (bad).Sub::read_rangefinder()
tests for this, so large outliers are rejected. This shouldminimizeeliminate test failures, and it also exercises the sq test inSub::read_rangefinder()
.Edit: I also fixed some test names and a few typos