| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 11.11111% with 24 lines in your changes missing coverage. Please review. @@ Coverage Diff @@
## 4.20 #11554 +/- ##
=========================================
Coverage 16.17% 16.17%
- Complexity 13294 13297 +3
=========================================
Files 5656 5656
Lines 498082 498090 +8
Branches 60415 60420 +5
=========================================
+ Hits 80569 80580 +11
+ Misses 408551 408545 -6
- Partials 8962 8965 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 14815 |
Sorry, something went wrong.
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
There was a problem hiding this comment.
code lgtm
not tested yet
Sorry, something went wrong.
|
[SF] Trillian test result (tid-14183)
|
Sorry, something went wrong.
…m volumes only The VR volumes resource count for PowerFlex volumes is updated here, resulting in resource count discrepancy (which is re-calculated through ResourceCountCheckTask later, and skips the VR volumes)
|
@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. |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 14913 |
Sorry, something went wrong.
|
@sureshanaparti a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-14295)
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, all smoke tests passed successfully with only powerflex primary storage.
Smoke tests completed. 139 look OK, 2 have errors, 0 did not run Only failed and skipped tests results shown below: Test | Result | Time (s) | Test File --- | --- | --- | --- test_02_revert_vm_snapshots | `Error` | 95.88 | test_vm_snapshot_kvm.py test_01_webhook_deliveries | `Failure` | 9.70 | test_webhook_delivery.py
The failed tests were executed manually and passed successfully:
test_vm_snapshot_kvm
Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | Status : SUCCESS === ok Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | Status : SUCCESS === ok Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | Status : SUCCESS === ok ---------------------------------------------------------------------- Ran 3 tests in 640.467s OK
test_webhook_delivery:
test_01_webhook_deliveries (tests.smoke.test_webhook_delivery.TestWebhookDelivery) ... === TestName: test_01_webhook_deliveries | Status : SUCCESS === ok ---------------------------------------------------------------------- Ran 1 test in 9.591s OK
Sorry, something went wrong.
|
Merging based on approvals and manual tests by @vladimirpetrov |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
This PR improves the smoke tests to support with ScaleIO/PowerFlex storage, and has some fixes.
It includes the following changes, in addition to the Marvin smoke tests.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Tested the updated smoke tests with ScaleIO/PowerFlex storage pool.
How did you try to break this feature and the system with this change?