Skip to content
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

Closed
Fish-Git opened this issue Jan 2, 2025 · 8 comments
Assignees
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected. W Possible Windows-only issue, that seems to occur more easily/frequently on Windows.

Comments

@Fish-Git
Copy link
Member

Fish-Git commented Jan 2, 2025

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), where runtest 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) whereas runtest expects it to be in mm/dd/yyyy format (e.g. 11/28/2024).

Same thing with the %time% batch file variable as well: in French it's 19:11:39,11 whereas runtestis written to expect 19: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.

@Fish-Git Fish-Git changed the title Bogus runtest Duration message due to host Language regional date/time format settings Bogus 'runtest' "Duration" message due to host Language regional date/time format settings Jan 2, 2025
@Fish-Git Fish-Git self-assigned this Jan 2, 2025
@Fish-Git Fish-Git added BUG The issue describes likely incorrect product functionality that likely needs corrected. W Possible Windows-only issue, that seems to occur more easily/frequently on Windows. labels Jan 2, 2025
Fish-Git added a commit that referenced this issue Jan 4, 2025
Resolves GitHub #698. (But NOT tested on any non-English system)
@Fish-Git
Copy link
Member Author

Fish-Git commented Jan 4, 2025

Fixed by commit a54ac18.

(But NOT tested on any non-English system)

@Fish-Git Fish-Git closed this as completed Jan 4, 2025
@wrljet
Copy link
Member

wrljet commented Jan 26, 2025

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.

Begin: "runtest -n * -t 2 -d ..\sdl-hyperion\tests" ...

On:     Fri 01/24/2025  at ~8,2:~10 AM

...

Ended at: Fri 01/24/2025  at ~8,2:~10 AM

Duration: 2 hours, 2 minutes

I've asked for information about the language/locale but haven't heard back yet.
Oh, and it all looks like normal English text.

Bill

@Fish-Git
Copy link
Member Author

Fish-Git commented Jan 26, 2025

(SIGH!)  Internationalization is such a PITA.  :(

I've asked for information about the language/locale but haven't heard back yet.

Ask them to send us the output of a echo %date% %time% command too.

(Is the duration at least right? It seems a tad on the high side.)

@wrljet
Copy link
Member

wrljet commented Jan 28, 2025

He's using US English and echo %date% %time% by itself display as expected.

... developing ...

@Fish-Git
Copy link
Member Author

Fish-Git commented Jan 29, 2025

Well I'm stumped!  :(

Maybe you can insert a set "DEBUG=1" just before runtest.cmd is invoked/called in your Hercules Helper script, and then reset it back to undefined afterwards (set "DEBUG=") so we can maybe see what's going on?

(Defining DEBUG will activate the %TRACE% statements sprinkled throughout the script and will hopefully provide us a clue as to where things are going wrong.)

@Fish-Git
Copy link
Member Author

Fish-Git commented Feb 9, 2025

@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.

@wrljet
Copy link
Member

wrljet commented Feb 9, 2025

Have been unable to reproduce locally.

@Fish-Git
Copy link
Member Author

Fish-Git commented Feb 9, 2025

Fine. Then I'll stop worrying about it. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG The issue describes likely incorrect product functionality that likely needs corrected. W Possible Windows-only issue, that seems to occur more easily/frequently on Windows.
Projects
None yet
Development

No branches or pull requests

2 participants