-
Notifications
You must be signed in to change notification settings - Fork 375
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
The collect_limit
test randomly fails in copr builds
#2076
Comments
jan-cerny
added a commit
to jan-cerny/openscap
that referenced
this issue
Jan 31, 2024
The function SEXP_list_length turns out to be an unreliable provider of information about the length of the list of the collected items. It is unclear what this function returns. Instead of using SEXP_list_length we will have a counter variable that will count the amount of collected items by the probe. Fixes: OpenSCAP#2076
cschuber
pushed a commit
to cschuber/openscap
that referenced
this issue
Feb 1, 2024
The function SEXP_list_length turns out to be an unreliable provider of information about the length of the list of the collected items. It is unclear what this function returns. Instead of using SEXP_list_length we will have a counter variable that will count the amount of collected items by the probe. Fixes: OpenSCAP#2076
cschuber
pushed a commit
to cschuber/openscap
that referenced
this issue
Feb 1, 2024
The function SEXP_list_length turns out to be an unreliable provider of information about the length of the list of the collected items. It is unclear what this function returns. Instead of using SEXP_list_length we will have a counter variable that will count the amount of collected items by the probe. Fixes: OpenSCAP#2076
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of Problem:
The test (or the code modifications) is unstable. We need to understand why and fix it before releasing the feature.
OpenSCAP Version:
maint-1.3
E.g. https://artifacts.dev.testing-farm.io/61bedc25-d4ff-4d5a-b114-e0605f3ddab3
The text was updated successfully, but these errors were encountered: