-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b20
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
---
---
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
---
- relates to
-
CODETOOLS-7903089 Polishing API usage a bit to make CODETOOLS-7902698 fix SE8 compatible
-
- Resolved
-