ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Commented] (IVY-1489) Still seeing *.lck files if ivy is aborted abruptly
Date Thu, 02 Nov 2017 03:03:01 GMT


Shawn Heisey commented on IVY-1489:

One of our seasoned devs figured out how to fix the Lucene build to protect against this problem,
using that alternate locking.  See LUCENE-6144 for info.

Is there anything that can be done in Ivy?  Perhaps switching the default locking mechanism?
 I have no idea whether that is likely to introduce problems for users.

> Still seeing *.lck files if ivy is aborted abruptly
> ---------------------------------------------------
>                 Key: IVY-1489
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>         Environment: Linux sauron 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.7.0_67"
> Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
>            Reporter: Shawn Heisey
>            Priority: Major
> IVY-1388 is still happening after upgrading to 2.3.0.
> For me, this is seen when building the lucene-solr project.  Frequently after starting
a build I will realize that I've typed the ant command line wrong, or that I haven't fixed
a problem correctly, so I will use ctrl-c to abort the build, fix the problem, and start it
back up.  Often the interruption will result in a .lck file being left behind and the build
hanging at "resolve:" until the .lck file is deleted.

This message was sent by Atlassian JIRA

View raw message