You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Matt Benson (JIRA)" <ji...@apache.org> on 2008/04/22 19:11:22 UTC

[jira] Created: (IO-164) LastModifiedFileComparatorTest goes into endless loop on OS X

LastModifiedFileComparatorTest goes into endless loop on OS X
-------------------------------------------------------------

                 Key: IO-164
                 URL: https://issues.apache.org/jira/browse/IO-164
             Project: Commons IO
          Issue Type: Test
          Components: Utilities
    Affects Versions: 1.4
            Reporter: Matt Benson
            Priority: Minor
             Fix For: 2.0


Apparently there is a bug in the OS X runtime such that writing zero bytes to a FileOutputStream, then closing it, does not modify the previous file.  For this reason the setup of this test never completes as it's waiting for an update of one file to result in that file having a later lastModified time than another file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (IO-164) LastModifiedFileComparatorTest goes into endless loop on OS X

Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Benson resolved IO-164.
----------------------------

    Resolution: Fixed

Committed revision 650580.

> LastModifiedFileComparatorTest goes into endless loop on OS X
> -------------------------------------------------------------
>
>                 Key: IO-164
>                 URL: https://issues.apache.org/jira/browse/IO-164
>             Project: Commons IO
>          Issue Type: Test
>          Components: Utilities
>    Affects Versions: 1.4
>            Reporter: Matt Benson
>            Priority: Minor
>             Fix For: 2.0
>
>
> Apparently there is a bug in the OS X runtime such that writing zero bytes to a FileOutputStream, then closing it, does not modify the previous file.  For this reason the setup of this test never completes as it's waiting for an update of one file to result in that file having a later lastModified time than another file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IO-164) LastModifiedFileComparatorTest goes into endless loop on OS X

Posted by "Matt Benson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IO-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Benson updated IO-164:
---------------------------

    Description: Apparently there is a bug in the OS X Java runtime such that writing zero bytes to a FileOutputStream, then closing it, does not modify the previous file.  For this reason the setup of this test never completes as it's waiting for an update of one file to result in that file having a later lastModified time than another file.  (was: Apparently there is a bug in the OS X runtime such that writing zero bytes to a FileOutputStream, then closing it, does not modify the previous file.  For this reason the setup of this test never completes as it's waiting for an update of one file to result in that file having a later lastModified time than another file.)

> LastModifiedFileComparatorTest goes into endless loop on OS X
> -------------------------------------------------------------
>
>                 Key: IO-164
>                 URL: https://issues.apache.org/jira/browse/IO-164
>             Project: Commons IO
>          Issue Type: Test
>          Components: Utilities
>    Affects Versions: 1.4
>            Reporter: Matt Benson
>            Priority: Minor
>             Fix For: 2.0
>
>
> Apparently there is a bug in the OS X Java runtime such that writing zero bytes to a FileOutputStream, then closing it, does not modify the previous file.  For this reason the setup of this test never completes as it's waiting for an update of one file to result in that file having a later lastModified time than another file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.