-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Refactoring smoke tests #11107
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
Refactoring smoke tests #11107
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11107 +/- ##
============================================
+ Coverage 16.57% 17.17% +0.60%
- Complexity 13968 15010 +1042
============================================
Files 5743 5869 +126
Lines 510494 521710 +11216
Branches 62075 63509 +1434
============================================
+ Hits 84617 89614 +4997
- Misses 416415 422039 +5624
- Partials 9462 10057 +595
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@slavkap can you check the license / lint errors. |
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 14476 |
|
@blueorangutan test |
|
@sureshanaparti a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
DaanHoogland
left a comment
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.
clgtm, and we need to trust @slavkap on this
|
[SF] Trillian test result (tid-13978)
|
* Refactor StorPool smoke tests * Marvin confing template for StorPool tests
Description
This PR refactors StorPool's smoke tests
Types of changes
How did you try to break this feature and the system with this change?
Executed all tests on the latest main branch