-
Notifications
You must be signed in to change notification settings - Fork 165
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
cleanup(tests): move filter compilation functions to sinsp_with_test_input #1911
cleanup(tests): move filter compilation functions to sinsp_with_test_input #1911
Conversation
/milestone 0.18.0 |
…input Signed-off-by: Luca Guerra <[email protected]>
ed73c09
to
a4791fb
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.
/approve
LGTM label has been added. Git tree hash: ed6cd07bbf9b94c1c9a2b55c6e8f4d56297291ee
|
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area tests
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
Recently I added
eval_filter()
to add an urgent regression test. This one is not urgent but since we hadtwothree different ways of evaluating a filter in tests I wanted to consolidate it in one single way.The
sinsp_with_test_input
way is preferred IMO because it uses a real inspector and some filterchecks require an inspector to be present and initialized in order to work.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: