-
Notifications
You must be signed in to change notification settings - Fork 275
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
Fix e2e ci by ignoring FOG warnings #7267
Conversation
Signed-off-by: Derek Nola <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7267 +/- ##
==========================================
- Coverage 23.70% 8.99% -14.72%
==========================================
Files 33 33
Lines 3392 3392
==========================================
- Hits 804 305 -499
- Misses 2541 3064 +523
+ Partials 47 23 -24
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Derek Nola <[email protected]>
Signed-off-by: Derek Nola <[email protected]>
Signed-off-by: Derek Nola <[email protected]>
Signed-off-by: Derek Nola <[email protected]>
Signed-off-by: Derek Nola <[email protected]>
Proposed Changes
The latest version of vagrant-libvirt current suffers from an error around FOG warnings being constantly produced on any call of
vagrant ssh
. For now we will simply remove these warnings from any output returnTypes of Changes
Verification
CI is once again green
Testing
Linked Issues
N/A nothing to QA
User-Facing Change
Further Comments