-
Notifications
You must be signed in to change notification settings - Fork 675
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
Failing unit tests test_ZeigerEvalHybrid
and in suite test_cnnflowcontroll
#2753
Comments
test_ZeigerEvalHybrid
test_ZeigerEvalHybrid
and in suite test_cnnflowcontroll
// the 5.7 and no previous should trunc to 5 5 is correct. (Changed result due to PR #2466) // the 5.8 and no previous should round up to 6 5 is correct. (Changed result due to PR #2466) It seems test cases (also in test_cnnflowcontroll) needs to be adapted to follow actual implementation changed by PR #2466. |
A while ago I refactord some parts of the code to get better understanding how it works. Maybe this could be helpful for your analysis somehow, otherwise just ignore my comment. 😺 Happy Christmas to everybody! 😺 |
I think @Slider0007 is right. Maybe I didn't fixed the unit tests. Will have a deeper look on it the next days. |
undertest.PointerEvalHybridNew has now 5 parameters. After the rewrite the tests are not fixed any more. First, in most cases we truncate instead of rounding. It's mostly the better way. But the early transition not working any more. (higher digit = 5.3 and lower digit is 9.7. Here the 9.7 => 9 and the 5.3 is an early transition and must be reduced to 4.) Will fix it the next days and rewrite the tests. |
The Problem
The unit test
test_ ZeigerEvalHybrid
is failing. In particular, three assertions fail:(returns 5 instead)
(returns 5 instead)
(returns 5 instead)
Also, multiple assertions are raised in the suite
test_cnnflowcontroll
.Version
Git rev 02138c4 (from 2023/11/22)
Logfile
Log of test_doFlowPP1:
test_doFlowPP1.txt
Log of test_doFlowPP2:
test_doFlowPP2.txt
Expected Behavior
No test failures.
Screenshots
No response
Additional Context
Note. I did not run the code natively on the esp but ported to post processing code to PC to be able to understand and debug the code. Later, I intend to improve issues, when the analog and digital counters are out of sync, but I'd like to have a solid test bed first.
The text was updated successfully, but these errors were encountered: