| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
clgtm
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.
There was a problem hiding this comment.
LGTM. Can be merged once GH actions passes
Thanks @vishesh92
In general, we need to be more careful with forward-merging 4.19 into main as build is failing regularly lately
Sorry, something went wrong.
Codecov ReportAttention: Patch coverage is 23.52941% with 26 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #9330 +/- ##
============================================
+ Coverage 4.17% 15.51% +11.34%
- Complexity 0 11939 +11939
============================================
Files 371 5492 +5121
Lines 30407 480616 +450209
Branches 5384 61684 +56300
============================================
+ Hits 1269 74575 +73306
- Misses 28994 397788 +368794
- Partials 144 8253 +8109
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.
There was a problem hiding this comment.
clgtm
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10239 |
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]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10246 |
Sorry, something went wrong.
* Fixup main build errors * Fixup flaky test * Address comments
| Back | FazBrowse Home | New Git URL |
Description
This PR fixes build errors on main branch
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?