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

An bug related to path where there is a blank space in the path name. #84

Closed
Zrrrrrrg opened this issue Sep 1, 2024 · 3 comments
Closed

Comments

@Zrrrrrrg
Copy link

Zrrrrrrg commented Sep 1, 2024

Version 0.9.6.2
It seems only occuring under the use of Linpack; Nothing wrong for Prime95, YCruncher New/Old.

When folder "CoreCycler-v0.9.6.2" is located under path like "D:\Test", it run properly;
When under path like ""D:\Test Test", the following error:
屏幕截图 2024-09-02 015926

"Can't find attribute 'Path' on this object."

I'm running under Chinese (zh-CN) environment. Maybe it relates to text encoding?

Log file attached:
Uploading CoreCycler_2024-09-02_02-02-31_LINPACK_2018_MEDIUM.log…

@sp00n
Copy link
Owner

sp00n commented Sep 2, 2024

I remember that I noticed something similar but eventually forgot about it. 😱

I do see a different kind of error though, where the Linpack window tries to open for a brief moment and immediately closes again, and then throws a different error.
I hope both issues actually have the same reason

@sp00n
Copy link
Owner

sp00n commented Sep 2, 2024

Can you try to replace "%fullPathToLoadExe%" with & \"%fullPathToLoadExe%\" in line 1100 of the script-corecycler.ps1 file?

Or just replace the whole line with:

        'command'             = 'cmd /C start /MIN "Linpack CoreCycler" powershell.exe -Command "$Host.UI.RawUI.WindowTitle = ''Linpack CoreCycler''; $PSDefaultParameterValues[''*:Encoding''] = ''utf8''; $env:OMP_NUM_THREADS = %OMP_NUM_THREADS%; %MKL_DEBUG_CPU_TYPE% $env:OMP_PLACES = ''CORES''; $env:OMP_PROC_BIND = ''SPREAD''; $env:MKL_DYNAMIC = ''FALSE''; $logFilePath = ''%logFilePath%''; if (!([IO.File]::Exists($logFilePath))) { [IO.File]::WriteAllLines($logFilePath, (Get-Date -Format HH:mm:ss)) }; & \"%fullPathToLoadExe%\" ''%configFilePath%'' | Tee-Object -FilePath $logFilePath -Append"'

It seemed to fix my problem, not sure if yours is fixed as well.

sp00n added a commit that referenced this issue Sep 6, 2024
- Fixed a bug where Linpack wouldn't start from a directory including a space (fixes #84)
- Fixed a bug where resuming after a crash with a "default" coresToTest order would result in an index out of bounds error (fixes #85)
- Also it didn't resume on the crashed core
- the config file's content is now put into the log file for easier debugging
- Fixed a bug where the log file for y-cruncher was actually using the naming scheme for Linpack (under unclear circumstances, but it happened at least once)
- Fixed a bug when the update check doesn't return any output at all (fixes #83)
sp00n added a commit that referenced this issue Sep 6, 2024
- Fixed a bug where Linpack wouldn't start from a directory including a space (fixes #84)
- Fixed a bug where resuming after a crash with a "default" coresToTest order would result in an index out of bounds error (fixes #85)
- Also it didn't resume on the crashed core
- the config file's content is now put into the log file for easier debugging
- Fixed a bug where the log file for y-cruncher was actually using the naming scheme for Linpack (under unclear circumstances, but it happened at least once)
- Fixed a bug when the update check doesn't return any output at all (fixes #83)
@sp00n
Copy link
Owner

sp00n commented Sep 6, 2024

This should now be fixed in the alpha3

@sp00n sp00n closed this as completed Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants