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

CI: lower FER/BER is always OK for regression testing. #185

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

gerhardbaer
Copy link

@gerhardbaer gerhardbaer commented Jan 3, 2024

Some AVX2 tests, and even SSE4 tests, randomly fail because the resulting error rates are lower than the reference. IMHO, lower error rates (BER, FER) should be accepted. Therefore, I am suggesting this patch to improve the PASS rate and accept lower BER/FER than reference.

Note: ignoring the lower error rates involve setting diff to zero. I am not quite sure of the expected behavior wrt. the sensibility computations. Otherwise, for LDPC tests, I need to set sensibility to 2.75 and weak rate to 0.87. Likewise, for TURBO_PRODtests, sensibility need to be increased to 2.75 too. Probably not a big deal in the end, but you get the idea. :)

Improve PASS rate of the regression testsuite by accepting lower error
rates, i.e. lower BER/FER vs. reference is always OK.

Signed-off-by: Gerhard Baer <Gerhard.Baer@protonmail.com>
@kouchy
Copy link
Member

kouchy commented Jan 4, 2024

I'm not very convinced by this :-/. Normally to avoid this problem, in the GitLab CI, we enabled the retry feature. Otherwise we can increase the required number of errors. The thing is: sometime, when the BER/FER increases it could be because of a bug.

@gerhardbaer
Copy link
Author

I agree that increasing BER/FER could be due to a bug. There is no change wrt. that case. However, decreasing BER/FER could actually mean an improvement and/or a bug fixed, isn't it?

@kouchy
Copy link
Member

kouchy commented Jan 5, 2024

Sorry it was not clear: I meant even if the BER/FER decreases it could be because of a bug (or a improvement) but it means that something changed in the code and we want to be notified to understand the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants