[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104698#comment-17104698 ] László Bodor commented on TEZ-4173: --- rechecked with all scenarios again, it works indeed (I was testing with my improvements in TEZ-4149, and it wasn't perfect at that time) current change looks good to me, +1 (I'm about to double-check TestRecovery again and then this can be committed) > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: Syed Shameerur Rahman >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.02.patch, TEZ-4173.03.patch, > TEZ-4173.reproduction.patch, am.jstack.log, surefire.jstack.log, > tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104394#comment-17104394 ] Syed Shameerur Rahman commented on TEZ-4173: [~abstractdog] Tested both testRecovery_HashJoin and testTwoRoundsRecoverying with all shutdown scenarios with 4 consecutive runs, Test passed in all four runs. Do you have any repro scenario? > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: Syed Shameerur Rahman >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.02.patch, TEZ-4173.03.patch, > TEZ-4173.reproduction.patch, am.jstack.log, surefire.jstack.log, > tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17104308#comment-17104308 ] László Bodor commented on TEZ-4173: --- [~srahman]: thanks, could you please also check testRecovery_HashJoin with all the shutdown scenarios? for me it's still hanging with your patch, however, testRecovery_OrderedWordCount seems to be solved > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: Syed Shameerur Rahman >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.02.patch, TEZ-4173.03.patch, > TEZ-4173.reproduction.patch, am.jstack.log, surefire.jstack.log, > tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103839#comment-17103839 ] Syed Shameerur Rahman commented on TEZ-4173: [~abstractdog] Can you please review TEZ-4173.03.patch. In my local testing i was able to get all the test scenarios in TezRecovery to pass. > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: Syed Shameerur Rahman >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.02.patch, TEZ-4173.03.patch, > TEZ-4173.reproduction.patch, am.jstack.log, surefire.jstack.log, > tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[
https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103810#comment-17103810
]
TezQA commented on TEZ-4173:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
33s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
58s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m
39s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
43s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s{color} | {color:green} The patch passed checkstyle in tez-dag {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s{color} | {color:green} tez-tests: The patch generated 0 new + 8 unchanged -
3 fixed = 8 total (was 11) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
37s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 4m
19s{color} | {color:green} tez-dag in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 41m 20s{color}
| {color:red} tez-tests in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 60m 20s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.8 Server=19.03.8 base:
https://builds.apache.org/job/PreCommit-TEZ-Build/417/artifact/out/Dockerfile |
| JIRA Issue | TEZ-4173 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13002535/TEZ-4173.02.patch |
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
checkstyle compile |
| uname | Linux 76db1170814f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | personality/tez.sh |
| git revision | master / 4e4b8e5 |
| Default Java | 1.8.0_252 |
| unit |
https://builds.apache.org/job/PreCommit-TEZ-Build/417/artifact/out/patch-unit-tez-tests.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-TEZ-Build/417/testReport/ |
| Max. process+thread count | 1352 (vs. ulimit of 5500) |
| modules | C: tez-dag tez-tests U: . |
| Console output |
https://builds.apache.org/job/PreCommit-TEZ-Build/417/console |
|
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103702#comment-17103702 ] Syed Shameerur Rahman commented on TEZ-4173: [~abstractdog] Sure, I will pick this one > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.reproduction.patch, > am.jstack.log, surefire.jstack.log, tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103699#comment-17103699 ] László Bodor commented on TEZ-4173: --- thanks for taking a look [~srahman]! shall I assign this jira to you? > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.reproduction.patch, > am.jstack.log, surefire.jstack.log, tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103694#comment-17103694 ] Syed Shameerur Rahman commented on TEZ-4173: [~abstractdog] Yes looks like a corner case, We can safely skip vertex initialization if tasks on that vertex started or setVertexParallelism is true (since it is called only once during vertex life cycle and it makes sure that the no. of tasks for that vertex are defined and won't change later). In TEZ-4173.01.patch instead of looking at numTask we should look for recoveryData.getVertexConfigurationDoneEvent().isSetParallelismCalled() and it requires modification of some tests added in TEZ-4140. > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > Attachments: TEZ-4173.01.patch, TEZ-4173.reproduction.patch, > am.jstack.log, surefire.jstack.log, tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[
https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103693#comment-17103693
]
TezQA commented on TEZ-4173:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
33s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
25s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m
40s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
37s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 41m 39s{color}
| {color:red} tez-tests in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
10s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 50m 22s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.8 Server=19.03.8 base:
https://builds.apache.org/job/PreCommit-TEZ-Build/416/artifact/out/Dockerfile |
| JIRA Issue | TEZ-4173 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13002518/TEZ-4173.reproduction.patch
|
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
checkstyle compile |
| uname | Linux b2603f58d3cc 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22
16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | personality/tez.sh |
| git revision | master / 4e4b8e5 |
| Default Java | 1.8.0_252 |
| unit |
https://builds.apache.org/job/PreCommit-TEZ-Build/416/artifact/out/patch-unit-tez-tests.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-TEZ-Build/416/testReport/ |
| Max. process+thread count | 1246 (vs. ulimit of 5500) |
| modules | C: tez-tests U: tez-tests |
| Console output |
https://builds.apache.org/job/PreCommit-TEZ-Build/416/console |
| versions | git=2.7.4 maven=3.3.9 findbugs=3.0.1 |
| Powered by | Apache Yetus 0.11.1 https://yetus.apache.org |
This message was automatically generated.
> TestRecovery flaky timeout on master
>
>
> Key: TEZ-4173
> URL: https://issues.apache.org/jira/browse/TEZ-4173
> Project: Apache Tez
> Issue Type: Bug
>Reporter: László Bodor
>Assignee: László Bodor
>Priority: Major
> Attachments: TEZ-4173.01.patch, TEZ-4173.reproduction.patch,
> am.jstack.log, surefire.jstack.log, tez4173.tar.gz
>
>
> application
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[
https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103453#comment-17103453
]
TezQA commented on TEZ-4173:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
35s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The 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. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 1m
9s{color} | {color:blue} Used deprecated FindBugs config; considering switching
to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
7s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 4m 6s{color}
| {color:red} tez-dag in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 14m 51s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | tez.dag.app.dag.impl.TestDAGRecovery |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.8 Server=19.03.8 base:
https://builds.apache.org/job/PreCommit-TEZ-Build/414/artifact/out/Dockerfile |
| JIRA Issue | TEZ-4173 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13002499/TEZ-4173.01.patch |
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
checkstyle compile |
| uname | Linux 6b8187d43c07 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | personality/tez.sh |
| git revision | master / 4e4b8e5 |
| Default Java | 1.8.0_252 |
| unit |
https://builds.apache.org/job/PreCommit-TEZ-Build/414/artifact/out/patch-unit-tez-dag.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-TEZ-Build/414/testReport/ |
| Max. process+thread count | 228 (vs. ulimit of 5500) |
| modules | C: tez-dag U: tez-dag |
| Console output |
https://builds.apache.org/job/PreCommit-TEZ-Build/414/console |
| versions | git=2.7.4 maven=3.3.9 findbugs=3.0.1 |
| Powered by | Apache Yetus 0.11.1 https://yetus.apache.org |
This message was automatically generated.
> TestRecovery flaky timeout on master
>
>
> Key: TEZ-4173
> URL: https://issues.apache.org/jira/browse/TEZ-4173
> Project: Apache Tez
> Issue Type: Bug
>Reporter: László Bodor
>
[jira] [Commented] (TEZ-4173) TestRecovery flaky timeout on master
[ https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103290#comment-17103290 ] László Bodor commented on TEZ-4173: --- seems like it's broken by TEZ-4140, or at least I've run the test successfully twice in a row with reverted TEZ-4140, and then it failed with the patch for the first time cc: [~srahman], if you have any pointers about this > TestRecovery flaky timeout on master > > > Key: TEZ-4173 > URL: https://issues.apache.org/jira/browse/TEZ-4173 > Project: Apache Tez > Issue Type: Bug >Reporter: László Bodor >Assignee: László Bodor >Priority: Major > Attachments: am.jstack.log, surefire.jstack.log, tez4173.tar.gz > > > application logs and junit output in [^tez4173.tar.gz] > one of the running AM's jstack is [^am.jstack.log] -- This message was sent by Atlassian Jira (v8.3.4#803005)
