-
Notifications
You must be signed in to change notification settings - Fork 149
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
[#2015] improvement(netty): Support Netty for MR integration test. #2016
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2016 +/- ##
============================================
+ Coverage 52.35% 52.87% +0.52%
- Complexity 2815 3424 +609
============================================
Files 452 518 +66
Lines 21217 28352 +7135
Branches 1950 2650 +700
============================================
+ Hits 11108 14992 +3884
- Misses 9401 12394 +2993
- Partials 708 966 +258 ☔ View full report in Codecov by Sentry. |
Test Results 2 926 files +31 2 926 suites +31 6h 15m 20s ⏱️ + 28m 15s Results for commit 1a64acf. ± Comparison against base commit f9b4c0e. This pull request removes 6 and adds 12 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
…using ShuffleBufferWithSkipList. (#2141) ### What changes were proposed in this pull request? Release duplicate block. #2016 solve this problem in client side. I think sendShuffeData may be retried, duplicated block still be reproduce. ### Why are the changes needed? Fix: #2105 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? test in cluster.
LGTM! wait for ci! |
… when using ShuffleBufferWithSkipList. (apache#2141) ### What changes were proposed in this pull request? Release duplicate block. apache#2016 solve this problem in client side. I think sendShuffeData may be retried, duplicated block still be reproduce. ### Why are the changes needed? Fix: apache#2105 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? test in cluster.
What changes were proposed in this pull request?
Support Netty for MR integration test.
Why are the changes needed?
Fix: #2015
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Integration tests themselves.