[p4] file modification time in the future causing gmake to loop

[Nathan_Tran@trendmicro.com]

Hi Everyone,

 

Recently, we had a developer submit a change to our Perforce server. The
developer and Perforce server are both located in Asia, and I'm located
in the US. When I synced his change to my workspace (which has the
"modtime" option enabled), I expected the file modification time to be
preserved but I didn't expect the file modification time to be
represented in the Asia time zone (i.e., the file modification time is
far ahead of my local system time). This behavior is causing my build to
run forever and recursively spitting out the following gmake warning:

 

gmake[1]: Entering directory
`/build/IWSS/3.1/redhat_as4/en/Source/src/pi_urlfilter/src'

gmake[1]: Warning: File `URLFilteringScanTask.cpp' has modification time
3.9e+04 s in the future

gmake[1]: Leaving directory
`/build/IWSS/3.1/redhat_as4/en/Source/src/pi_urlfilter/src'

gmake[1]: Entering directory
`/build/IWSS/3.1/redhat_as4/en/Source/src/pi_urlfilter/src'

gmake[1]: Warning: File `URLFilteringScanTask.cpp' has modification time
3.9e+04 s in the future

gmake[1]: Leaving directory
`/build/IWSS/3.1/redhat_as4/en/Source/src/pi_urlfilter/src'

 

I am able to get around this by disabling my workspace's "modtime"
option so that file modification times are set to the time of the sync.

 

Anyhow, can anyone tell me if this is expected behavior when running and
using Perforce across different time zones? I actually expected Perforce
to convert the file modification time to my local time zone when files
are synced to my workspace. Are there any other solutions besides
disabling the "modtime" option?

 

Thanks,

Nathan

 

 



TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.