[MINOR] chore(ci): Add Tez pipeline #862
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaijchen
changed the title
Codecov Report
@@ Coverage Diff @@
## master #862 +/- ##
============================================
+ Coverage 56.58% 58.72% +2.14%
- Complexity 2174 2175 +1
============================================
Files 327 307 -20
Lines 15977 13621 -2356
Branches 1262 1263 +1
============================================
- Hits 9040 7999 -1041
+ Misses 6429 5185 -1244
+ Partials 508 437 -71 see 23 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Merged to master. thanks @kaijchen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add the pipeline of Tez
Why are the changes needed?
We should verify the code of Tez
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No need.