Uploaded image for project: 'Code Tools'
  1. Code Tools
  2. CODETOOLS-7902698

Collision of zero timestamp as a special value with use in filesystems

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: tools
    • Labels:

      Description

      My colleague Jonathan Joo reports:

      ---
      Currently, jtharness is using a timestamp of zero as a special value, as the default canonical timestamp. However, this is not particularly robust and can interfere with other systems which may choose to use zero as its default timestamp as well. (For example, at google, we faced failures in certain systems due to both using the same zero timestamp as a special value, and we worked around it by changing ours to another value.) However, it would be helpful to change the code such that this error should never occur and is not dependent on the system it is being run on.

      Notably, this affects the following files and variables:

      src/com/sun/javatest/ExcludeListUpdateHandler.java:
      - localFileLastModified, remoteURLLastModified

      src/com/sun/javatest/InterviewParameters.java
      - currFileLastModified

      src/com/sun/javatest/TRT_TreeNode.java
      - lastScanDate
      ---

        Attachments

          Activity

            People

            Assignee:
            dbessono Dmitry Bessonov
            Reporter:
            martin Martin Buchholz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: