-
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): add some exceptions in sinsp test framework #2140
Conversation
Signed-off-by: Andrea Terzolo <andreaterzolo3@gmail.com>
Perf diff from master - unit tests
Heap diff from master - unit tests
Heap diff from master - scap file
Benchmarks diff from master
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2140 +/- ##
==========================================
- Coverage 74.46% 74.45% -0.01%
==========================================
Files 254 254
Lines 33340 33345 +5
Branches 5724 5723 -1
==========================================
+ Hits 24827 24828 +1
+ Misses 8508 8493 -15
- Partials 5 24 +19
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
LGTM label has been added. Git tree hash: f22fb43f2c073474825f54454bfc42e7174da15f
|
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 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:
add some exceptions in sinsp test framework
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: