Skip to content

TEZ-4705: Make Yetus test4tests vote for -0 instead of -1 for Tez - #481

Closed
Aggarwal-Raghav wants to merge 1 commit into
apache:masterfrom
Aggarwal-Raghav:TEZ-4705
Closed

TEZ-4705: Make Yetus test4tests vote for -0 instead of -1 for Tez#481
Aggarwal-Raghav wants to merge 1 commit into
apache:masterfrom
Aggarwal-Raghav:TEZ-4705

Conversation

@Aggarwal-Raghav

Copy link
Copy Markdown
Contributor

No description provided.

Comment threadbuild-tools/test-patch.sh Outdated
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.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where can I see the effect of this change?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess no where 😬, only github emoji by yetus are coming.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on JIRA also, no color and in github also no orange color. But i think its better to keep it orange. WDYT?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, we can consider removing test-patch.sh later if it turns out we don't use it at all

@Aggarwal-RaghavAggarwal-RaghavApr 15, 2026

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm,
Here is the scenario i'm thinking:

  1. If in a PR new tests are added:
  • UT passed (unit): +1 green
  • UT failed (unit): -1 red
  • test4testsL +1 green
  1. 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.

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec5m 2sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+0 🆗shelldocs0m 0sShelldocs was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
_ master Compile Tests _
_ Patch Compile Tests _
+1 💚codespell0m 5sNo new issues.
+1 💚blanks0m 0sThe patch has no blanks issues.
+1 💚shellcheck0m 2sNo new issues.
_ Other Tests _
+1 💚asflicense0m 20sThe patch does not generate ASF License warnings.
5m 50s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/1/artifact/out/Dockerfile
GITHUB PR#481
Optional Testsdupname asflicense codespell detsecrets shellcheck shelldocs
unameLinux 344de02a5d04 5.15.0-173-generic #183-Ubuntu SMP Fri Mar 6 13:29:34 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-481/src/.yetus/personality.sh
git revisionmaster / 573c3bb
Max. process+thread count51 (vs. ulimit of 5500)
modulesC: . U: .
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/1/console
versionsgit=2.43.0 maven=3.9.14 codespell=2.4.1 shellcheck=0.7.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

I'll make 1 checkstyle fix i.e. java change to trigger the test4tests

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 11sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+0 🆗shelldocs0m 0sShelldocs was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
-0 ⚠️test4tests0m 0sThe patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.
_ master Compile Tests _
+0 🆗mvndep0m 29sMaven dependency ordering for branch
+1 💚mvninstall2m 57smaster passed
+1 💚compile1m 29smaster passed
+1 💚checkstyle1m 4smaster passed
+1 💚javadoc1m 12smaster passed
+0 🆗spotbugs0m 59stez-dag in master has 749 extant spotbugs warnings.
+0 🆗spotbugs3m 54sroot in master has 1935 extant spotbugs warnings.
_ Patch Compile Tests _
+0 🆗mvndep0m 5sMaven dependency ordering for patch
+1 💚mvninstall2m 28sthe patch passed
+1 💚codespell1m 0sNo new issues.
+1 💚compile1m 38sthe patch passed
+1 💚javac1m 38sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
+1 💚checkstyle0m 25stez-dag: The patch generated 0 new + 111 unchanged - 2 fixed = 111 total (was 113)
+1 💚checkstyle0m 35sroot: The patch generated 0 new + 111 unchanged - 2 fixed = 111 total (was 113)
+1 💚shellcheck0m 2sNo new issues.
+1 💚javadoc1m 18sthe patch passed
+1 💚spotbugs5m 13sthe patch passed
_ Other Tests _
+1 💚unit4m 50stez-dag in the patch passed.
+1 💚unit59m 48sroot in the patch passed.
+1 💚asflicense0m 52sThe patch does not generate ASF License warnings.
92m 40s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/2/artifact/out/Dockerfile
GITHUB PR#481
Optional Testsdupname asflicense codespell detsecrets shellcheck shelldocs javac javadoc unit spotbugs checkstyle compile
unameLinux 11f22fb961e3 5.15.0-173-generic #183-Ubuntu SMP Fri Mar 6 13:29:34 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-481/src/.yetus/personality.sh
git revisionmaster / 035e159
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/2/testReport/
Max. process+thread count1336 (vs. ulimit of 5500)
modulesC: tez-dag . U: .
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/2/console
versionsgit=2.43.0 maven=3.9.14 spotbugs=4.9.3 codespell=2.4.1 shellcheck=0.7.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

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;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can revert this when the patch is fully finalized and approved

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@tez-yetus

Copy link
Copy Markdown

💔 -1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 11sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+0 🆗shelldocs0m 0sShelldocs was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
+1 💚test4tests0m 0sThe patch appears to include 1 new or modified test files.
_ master Compile Tests _
+0 🆗mvndep0m 29sMaven dependency ordering for branch
+1 💚mvninstall2m 39smaster passed
+1 💚compile1m 35smaster passed
+1 💚checkstyle1m 2smaster passed
+1 💚javadoc1m 26smaster passed
+0 🆗spotbugs0m 53stez-api in master has 545 extant spotbugs warnings.
+0 🆗spotbugs3m 50sroot in master has 1935 extant spotbugs warnings.
_ Patch Compile Tests _
+0 🆗mvndep0m 6sMaven dependency ordering for patch
+1 💚mvninstall2m 21sthe patch passed
+1 💚codespell0m 48sNo new issues.
+1 💚compile1m 32sthe patch passed
+1 💚javac1m 32sthe patch passed
+1 💚blanks0m 0sThe patch has no blanks issues.
+1 💚checkstyle0m 53sthe patch passed
+1 💚shellcheck0m 2sNo new issues.
+1 💚javadoc1m 14sthe patch passed
+1 💚spotbugs5m 0sthe patch passed
_ Other Tests _
-1 ❌unit1m 59s/patch-unit-tez-api.txttez-api in the patch passed.
-1 ❌unit61m 52s/patch-unit-root.txtroot in the patch passed.
+1 💚asflicense0m 55sThe patch does not generate ASF License warnings.
90m 52s
ReasonTests
Failed junit teststez.common.TestTezCommonUtils
tez.common.TestTezCommonUtils
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/3/artifact/out/Dockerfile
GITHUB PR#481
Optional Testsdupname asflicense codespell detsecrets shellcheck shelldocs javac javadoc unit spotbugs checkstyle compile
unameLinux 20f709d1daeb 5.15.0-173-generic #183-Ubuntu SMP Fri Mar 6 13:29:34 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-481/src/.yetus/personality.sh
git revisionmaster / 462e10e
Default JavaUbuntu-21.0.10+7-Ubuntu-124.04
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/3/testReport/
Max. process+thread count1348 (vs. ulimit of 5500)
modulesC: tez-api . U: .
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/3/console
versionsgit=2.43.0 maven=3.9.14 spotbugs=4.9.3 codespell=2.4.1 shellcheck=0.7.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@tez-yetus

Copy link
Copy Markdown

🎊 +1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 11sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+0 🆗detsecrets0m 0sdetect-secrets was not available.
+0 🆗shelldocs0m 0sShelldocs was not available.
+1 💚@author0m 0sThe patch does not contain any @author tags.
_ master Compile Tests _
_ Patch Compile Tests _
+1 💚codespell0m 6sNo new issues.
+1 💚blanks0m 0sThe patch has no blanks issues.
+1 💚shellcheck0m 0sNo new issues.
_ Other Tests _
+1 💚asflicense0m 18sThe patch does not generate ASF License warnings.
0m 54s
SubsystemReport/Notes
DockerClientAPI=1.54 ServerAPI=1.54 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/4/artifact/out/Dockerfile
GITHUB PR#481
Optional Testsdupname asflicense codespell detsecrets shellcheck shelldocs
unameLinux 12a60895c737 5.15.0-173-generic #183-Ubuntu SMP Fri Mar 6 13:29:34 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personality/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-481/src/.yetus/personality.sh
git revisionmaster / faf4957
Max. process+thread count57 (vs. ulimit of 5500)
modulesC: . U: .
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/4/console
versionsgit=2.43.0 maven=3.9.14 codespell=2.4.1 shellcheck=0.7.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@abstractdog
abstractdog self-requested a review April 28, 2026 13:29
@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

i'll rebase and force push

@abstractdog

Copy link
Copy Markdown
Contributor

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! 🚀

@ayushtknayushtkn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

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 -1 as overall yetus outcome.
One can argue for Java changes if no UT is there then -1 is correct behaviour but I don't see any file extension based decision making in yetus.

In build-tools/test-patch.sh checkTests(), the behaviour is if "documentation" keyword is present in PR title then it will not give -1 (I've not tested this behaviour)

 testReferences=`$GREP -c -i -e '^+++.*/test' $PATCH_DIR/patch`
echo "There appear to be $testReferences test files referenced in the patch."
if [[ $testReferences == 0 ]] ; then
if [[ $JENKINS == "true" ]] ; then
patchIsDoc=`$GREP -c -i 'title="documentation' $PATCH_DIR/jira`
if [[ $patchIsDoc != 0 ]] ; then
echo "The patch appears to be a documentation patch that doesn't require tests."
JIRA_COMMENT="$JIRA_COMMENT
{color:green}+0 tests included{color}. The patch appears to be a documentation patch that doesn't require tests."
return 0
fi
fi
JIRA_COMMENT="$JIRA_COMMENT

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.

@tez-yetus

Copy link
Copy Markdown

💔 -1 overall

VoteSubsystemRuntimeLogfileComment
+0 🆗reexec0m 0sDocker mode activated.
-1 ❌docker8m 40sDocker failed to build run-specific yetus/tez:tp-11071}.
SubsystemReport/Notes
GITHUB PR#481
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-481/5/console
versionsgit=2.34.1
Powered byApache Yetus 0.15.1 https://yetus.apache.org

This message was automatically generated.

@abstractdog

Copy link
Copy Markdown
Contributor

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 -1 as overall yetus outcome. One can argue for Java changes if no UT is there then -1 is correct behaviour but I don't see any file extension based decision making in yetus.

In build-tools/test-patch.sh checkTests(), the behaviour is if "documentation" keyword is present in PR title then it will not give -1 (I've not tested this behaviour)

 testReferences=`$GREP -c -i -e '^+++.*/test' $PATCH_DIR/patch`
echo "There appear to be $testReferences test files referenced in the patch."
if [[ $testReferences == 0 ]] ; then
if [[ $JENKINS == "true" ]] ; then
patchIsDoc=`$GREP -c -i 'title="documentation' $PATCH_DIR/jira`
if [[ $patchIsDoc != 0 ]] ; then
echo "The patch appears to be a documentation patch that doesn't require tests."
JIRA_COMMENT="$JIRA_COMMENT
{color:green}+0 tests included{color}. The patch appears to be a documentation patch that doesn't require tests."
return 0
fi
fi
JIRA_COMMENT="$JIRA_COMMENT

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.

no strong opinions about this, ultimately it's about the confetti_ball vs. broken_heart icon on top of the yetus report, but it doesn't break the pipeline, and lets the reviewer decide whether the patch is correct and merge, I'm fine with keeping as is

@Aggarwal-Raghav

Copy link
Copy Markdown
ContributorAuthor

ok, closing this PR then

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@Aggarwal-Raghav@tez-yetus@abstractdog@ayushtkn