You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Gintas Grigelionis (JIRA)" <ji...@apache.org> on 2017/09/01 16:56:00 UTC

[jira] [Updated] (IVY-401) Ivy silently does the wrong thing when /tmp is full

     [ https://issues.apache.org/jira/browse/IVY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gintas Grigelionis updated IVY-401:
-----------------------------------
    Summary: Ivy silently does the wrong thing when /tmp is full  (was: Ivy silently does the wrong thing when /tmp is full.)

> Ivy silently does the wrong thing when /tmp is full
> ---------------------------------------------------
>
>                 Key: IVY-401
>                 URL: https://issues.apache.org/jira/browse/IVY-401
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.4.1
>         Environment: Linux
>            Reporter: John Williams
>            Priority: Minor
>
> I ran into a case where Ivy was mysteriously failing to consider revision 1.0.9999-local of a module called lcc.util.nlp.  Inspecting the logs revealed that the problem was a lack of disk space:
> WARN: problem while downloading ivy file: /home/smcdaniel/.ivy/local/lcc/lcc.util.nlp/1.0.9999-local/ivys/ivy.xml to /tmp/ivy50398xml: No space left on device
> Unfortunately this warning was buried in all the output that Ivy generates!  This suggests two possible improvements to me: fail loudly when there is an error saving downloaded data (as opposed to reading the data from the repository), and avoid using /tmp at all for ivy.xml files.  (I assume a temp dir is used to avoid having partial ivy.xml files in the file system, but that's not 100% reliable on systems where /tmp is on a different physical volume  than ~/.ivy, and it seems unnecessary to use a file at all since ivy.xml files are never very large.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)