-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bogus 'runtest'
"Duration" message due to host Language regional date/time format settings
#698
Comments
runtest
Duration message due to host Language regional date/time format settings'runtest'
"Duration" message due to host Language regional date/time format settings
Resolves GitHub #698. (But NOT tested on any non-English system)
Fixed by commit a54ac18. (But NOT tested on any non-English system) |
Fish, I just had another Hercules-Helper for Windows user send me a log file for an unrelated issue, and I noticed these oddball looking timestamps.
...
I've asked for information about the language/locale but haven't heard back yet. Bill |
(SIGH!) Internationalization is such a PITA.
Ask them to send us the output of a (Is the duration at least right? It seems a tad on the high side.) |
He's using US English and ... developing ... |
Well I'm stumped! Maybe you can insert a (Defining |
@wrljet Status? Does this issue need to be re-opened? Do we still have unresolved problems? Or can I remove it from my notifications list? Thanks. |
Have been unable to reproduce locally. |
Fine. Then I'll stop worrying about it. Thanks. |
I happened to notice in someone's Hercules Helper log file, the following "Duration" message after the
make check
step (near the very end of the log file), whereruntest
is invoked to run all of Hercules's quality assurance tests to verify that a properly working Hercules executable was just built:Duration: 21 hours, 48 minutes, 21 seconds
Suspecting that this was an obvious bogus duration (our entire suite of tests usuall only take a minute or three at the most!), I asked Bill to look into it. He responded with:
which we both suspect is being caused by the fact that the user's host o/s (Windows 11) Language setting was set to a non-English language (in this case, French), since different regions and languages format their dates and times differently than the way we do here in the U.S.
In French for example, the
%date%
batch variable is formatted as e.g. "28/11/2024" (i.e.dd/mm/yyyy
) whereasruntest
expects it to be inmm/dd/yyyy
format (e.g.11/28/2024
).Same thing with the
%time%
batch file variable as well: in French it's19:11:39,11
whereasruntest
is written to expect19:11:39.11
instead. (notice the comma and the period)This issue is being created to record the fact that this oversight (BUG!) needs to eventually be fixed.
The text was updated successfully, but these errors were encountered: