This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
CSM BDS: findJobTimeRange.py is dependent on date+time format #995
Comments
To fix the date+time format in the script, modify the two lines: Replace the blank between date and time with the letter T.
|
Found another script that also has similar date+time format hard coded:
That needs to be modified similarly:
|
thanh-lam
added a commit
to thanh-lam/CAST
that referenced
this issue
Mar 4, 2021
2 tasks
A 3rd script that uses old date+time format that needs to be corrected:
|
williammorrison2
added a commit
to williammorrison2/CAST
that referenced
this issue
Aug 17, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
The python script
findJobTimeRange.py
displaysbegin_time
,history.end_time
, and related info for an allocation. As described in #992, the date+time format is required to be updated to "yyyy-MM-ddThh:mm:ss.SSSZ". The problem is thatfindJobTimeRange.py
defined this date format based on the old date string "yyyy-MM-dd hh:mm:ss.SSSZ". This caused a failure:To Reproduce
Steps to reproduce the behavior:
Expected behavior
Example of a successful run:
Environment (please complete the following information):
Additional context
Following two lines in findJobTimeRange.py are where date format is defined.
Issue Source:
Because the date format is "hard coded" in the script. It required to be changed every time the date+time format is changed.
The text was updated successfully, but these errors were encountered: