Fixed issue with reporter failing to initialize by jgebal · Pull Request #1354 · utPLSQL/utPLSQL
Test Results
1 files 103 suites 1m 49s ⏱️
1 118 tests 1 114 ✅ 4 💤 0 ❌
1 122 runs 1 114 ✅ 8 💤 0 ❌
Results for commit cbd68ee.
♻️ This comment has been updated with latest results.
Codecov Report
✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.04%. Comparing base (a839888) to head (cbd68ee).
Additional details and impacted files
@@ Coverage Diff @@ ## develop #1354 +/- ## =========================================== - Coverage 95.05% 95.04% -0.01% =========================================== Files 112 112 Lines 5495 5492 -3 Branches 30 30 =========================================== - Hits 5223 5220 -3 Misses 272 272
| Flag | Coverage Δ | |
|---|---|---|
| 19se | 95.09% <100.00%> (-0.01%) |
⬇️ |
| 21XE | 95.24% <100.00%> (-0.01%) |
⬇️ |
| 23-free | 94.99% <100.00%> (-0.01%) |
⬇️ |
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.
🚀 New features to boost your workflow:
- ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Fixing issue with reporter failing to initialize
Fixed issue with reporter failing to initialize
