Re: [HTCondor-users] job event logs and time zones

[David Schultz <david.schultz@xxxxxxxxxxxxxxxx>]

Hi Tim,

I needed to use DEFAULT_USERLOG_FORMAT_OPTIONS, but yes, that fixes it. It's unfortunate that there isn't a knob in the submit file and it's global, so it affects all users. We decided that was acceptable in our case.

Thanks,

David

On Tue, Jun 4, 2024 at 6:44âAM Tim Theisen <tim@xxxxxxxxxxx> wrote:

Hello David,

Perhaps setting the event log time timestamps to UTC would fix your issue.

https://htcondor.readthedocs.io/en/latest/admin-manual/configuration-macros.html#EVENT_LOG_FORMAT_OPTIONS

...Tim

On 6/3/24 17:14, David Schultz wrote:
> Hi,
>
> I'm using a saved job event log for running some tests in a python
> application, and noticed that opening the log in different time zones
> gave a different event timestamp. My guess is that this is because
> the local time was written into the job event log, and not the unix time.
>
> Is there any good way to "fix" this so it's consistent across time
> zones, at least when it's read back using the python api?
>
> I also wonder how job event logs handle daylight savings time, and the
> discontinuity that happens there in local time.
>
> Best,
> David Schultz
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

--
Tim Theisen (he, him, his)
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736