fix: catch ClosedByInterruptException and handle it at debug/info #924
GitHub Actions / Integration Tests Coverage Report
completed
Oct 5, 2023 in 0s
Integration Tests Coverage Report
Integration Tests Coverage Report
| File | Coverage | Lines | Branches | |
|---|---|---|---|---|
| All files | 67% |
76% |
59% |
✅ |
| com.aws.greengrass.logmanager.services.DiskSpaceManagementService | 47% |
55% |
40% |
❌ |
| com.aws.greengrass.logmanager.CloudWatchLogsUploader | 42% |
42% |
41% |
❌ |
| com.aws.greengrass.logmanager.LogManagerService | 81% |
93% |
70% |
✅ |
| com.aws.greengrass.logmanager.LogManagerService$CurrentProcessingFileInformation | 46% |
55% |
37% |
❌ |
| com.aws.greengrass.logmanager.PositionTrackingBufferedReader | 72% |
82% |
63% |
✅ |
| com.aws.greengrass.logmanager.CloudWatchAttemptLogsProcessor | 70% |
74% |
66% |
✅ |
| com.aws.greengrass.logmanager.util.ConfigUtil | 48% |
61% |
35% |
❌ |
| com.aws.greengrass.logmanager.util.CloudWatchClientFactory | 100% |
100% |
0% |
✅ |
| com.aws.greengrass.logmanager.model.CloudWatchAttemptLogInformation | 100% |
100% |
0% |
✅ |
| com.aws.greengrass.logmanager.model.EventType | 100% |
100% |
0% |
✅ |
| com.aws.greengrass.logmanager.model.ComponentType | 100% |
100% |
0% |
✅ |
| com.aws.greengrass.logmanager.model.ProcessingFiles | 76% |
85% |
68% |
✅ |
| com.aws.greengrass.logmanager.model.LogFile | 40% |
46% |
34% |
❌ |
| com.aws.greengrass.logmanager.model.LogFileGroup | 64% |
74% |
53% |
✅ |
Minimum allowed coverage is 58%
Generated by 🐒 cobertura-action against 8b3e8d7
Loading