[
https://issues.apache.org/jira/browse/TEZ-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated TEZ-4649:
------------------------------
Description:
tested by:
{code}
mvn clean install -Denforcer.skip=true -nsu -Dtest=TestAnalyzer#testWithATS
-pl ./tez-tools/analyzers/job-analyzer -am
{code}
git bisected, and double-checked before and after this commit:
{code}
commit 03b5f1d68ed30d214d0a0aa3e6ec9fe67777372d
TEZ-4636: Move to JDK-21+ (#418)
{code}
I discovered this issue while testing jersey upgrade in the scope of TEZ-4648
I'm afraid we don't run all the unit tests in case of a root pom.xml change
either, otherwise TEZ-4636 PR (https://github.com/apache/tez/pull/418), should
have shown this problem, which it hasn't (only TestRecovery)
bad (with JDK21 patch, on JDK21 locally):
good (without JDK21 patch, onJDK17 locally):
[^GOOD_TEZ_4649_org.apache.tez.analyzer.TestAnalyzer-output.txt]
was:
tested by:
{code}
mvn clean install -Denforcer.skip=true -nsu -Dtest=TestAnalyzer#testWithATS
-pl ./tez-tools/analyzers/job-analyzer -am
{code}
git bisected, and double-checked before and after this commit:
{code}
commit 03b5f1d68ed30d214d0a0aa3e6ec9fe67777372d
TEZ-4636: Move to JDK-21+ (#418)
{code}
I discovered this issue while testing jersey upgrade in the scope of TEZ-4648
I'm afraid we don't run all the unit tests in case of a root pom.xml change
either, otherwise TEZ-4636 PR (https://github.com/apache/tez/pull/418), should
have shown this problem, which it hasn't (only TestRecovery)
bad (with JDK21 patch, on JDK21 locally):
good (without JDK21 patch, onJDK17 locally):
> Java21 upgrade has broken TestAnalyzer#testWithATS
> --------------------------------------------------
>
> Key: TEZ-4649
> URL: https://issues.apache.org/jira/browse/TEZ-4649
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: László Bodor
> Priority: Major
> Attachments:
> GOOD_TEZ_4649_org.apache.tez.analyzer.TestAnalyzer-output.txt
>
>
> tested by:
> {code}
> mvn clean install -Denforcer.skip=true -nsu -Dtest=TestAnalyzer#testWithATS
> -pl ./tez-tools/analyzers/job-analyzer -am
> {code}
> git bisected, and double-checked before and after this commit:
> {code}
> commit 03b5f1d68ed30d214d0a0aa3e6ec9fe67777372d
> TEZ-4636: Move to JDK-21+ (#418)
> {code}
> I discovered this issue while testing jersey upgrade in the scope of TEZ-4648
> I'm afraid we don't run all the unit tests in case of a root pom.xml change
> either, otherwise TEZ-4636 PR (https://github.com/apache/tez/pull/418),
> should have shown this problem, which it hasn't (only TestRecovery)
> bad (with JDK21 patch, on JDK21 locally):
> good (without JDK21 patch, onJDK17 locally):
> [^GOOD_TEZ_4649_org.apache.tez.analyzer.TestAnalyzer-output.txt]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
