You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2021/03/13 14:23:45 UTC
[Bug 64733] Deadlock in JUnitLauncher Task when using
LegacyXmlResultFormatter
https://bz.apache.org/bugzilla/show_bug.cgi?id=64733
Jaikiran Pai <ja...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |1.10.10
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jaikiran Pai <ja...@apache.org> ---
I tried a few things (including what you suggested about explicitly throwing an
IOException just for the sake of reproducing this issue), but I haven't been
able to reproduce this deadlock. But like Stefan says, it doesn't mean that
this code has an issue.
So I went ahead and added a potential fix to this in upstream master branch.
The commit is
https://github.com/apache/ant/commit/71c230dd93ab98df16c61cc949fd8ffe3c8cbaa2.
Given that I haven't been able to reproduce this, I won't be able to verify if
this indeed works. We publish an Ant nightly build here
https://ci-builds.apache.org/job/Ant/job/Ant_Nightly/lastSuccessfulBuild/artifact/.
An hour or two from now, it should have the nightly distribution which contains
this fix. It would be great if you could give tihs a try on your setup where
this seems to be happening regularly. If you do give it a try there, please do
report back with your observations.
For now, I'm marking this issue as resolved. If however, your tests show that
this hasn't fixed the issue, please feel free to reopen.
--
You are receiving this mail because:
You are the assignee for the bug.