TEZ-4705: Make Yetus test4tests vote for -0 instead of -1 for Tez#481
TEZ-4705: Make Yetus test4tests vote for -0 instead of -1 for Tez#481Aggarwal-Raghav wants to merge 1 commit intoapache:masterfrom
Conversation
| JIRA_COMMENT="$JIRA_COMMENT | ||
|
|
||
| {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. | ||
| {color:orange}-0 tests included{color}. The patch doesn't appear to include any new or modified tests. |
There was a problem hiding this comment.
Used reference for color from yetus project.
There was a problem hiding this comment.
where can I see the effect of this change?
There was a problem hiding this comment.
i guess no where 😬, only github emoji by yetus are coming.
There was a problem hiding this comment.
on JIRA also, no color and in github also no orange color. But i think its better to keep it orange. WDYT?
There was a problem hiding this comment.
okay, we can consider removing test-patch.sh later if it turns out we don't use it at all
There was a problem hiding this comment.
hmm,
Here is the scenario i'm thinking:
- If in a PR new tests are added:
- UT passed (unit): +1 green
- UT failed (unit): -1 red
- test4testsL +1 green
- If no new UT were added:
- test4tests): -0 orange irrespective of UT failure as they are handled be unit
I'm little confused. let me test few things.
|
🎊 +1 overall
This message was automatically generated. |
|
I'll make 1 checkstyle fix i.e. java change to trigger the |
|
🎊 +1 overall
This message was automatically generated. |
| public DAGStatusBuilder getDAGStatus(Set<StatusGetOpts> statusOptions, | ||
| long timeoutMillis) throws TezException { | ||
| long timeoutNanos = timeoutMillis * 1000l * 1000l; | ||
| long timeoutNanos = timeoutMillis * 1000L * 1000L; |
There was a problem hiding this comment.
I think you can revert this when the patch is fully finalized and approved
035e159 to
462e10e
Compare
|
💔 -1 overall
This message was automatically generated. |
462e10e to
faf4957
Compare
|
🎊 +1 overall
This message was automatically generated. |
|
i'll rebase and force push |
thanks, feel free to rebase anything which was blocked on github actions issue and I'll check them again as soon as I can! 🚀 |
faf4957 to
ef9d479
Compare
ayushtkn
left a comment
There was a problem hiding this comment.
What is the motivation behind this?
This has been discussed in hadoop as well & blocked every time:
apache/hadoop#6937 (comment)
The ticket mentioned in the Jira
This is the same as HADOOP-16611 but for Tez
This is also resolved as Not a Problem
The PR linked was also abandoned:
apache/hadoop#1523 (comment)
@ayushtkn , for changes in README, pom, Jenkinsfile or Dockerfile, it doesn't contains UT and it give In All in all its a PMC's decision what behaviour is more favourable for the project in long run . Please discuss among yourselves and let me know if I need to close this PR. |
|
💔 -1 overall
This message was automatically generated. |
No description provided.