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

Misc. bug: test case "Server / server-windows (pull_request) " failed in PR checks, error:"The term 'pytest' is not recognized as a name of a cmdlet, function, script file, or executable program" #10554

Closed
leo-pony opened this issue Nov 28, 2024 · 2 comments

Comments

@leo-pony
Copy link
Contributor

leo-pony commented Nov 28, 2024

Name and Version

Test case "Server / server-windows (pull_request) " failed in PR checks, error:"The term 'pytest' is not recognized as a name of a cmdlet, function, script file, or executable program".

The PR that affected by this issue: #10519.
This issue may have relationship with PR #10416(server : replace behave with pytest) .

Operating systems

Linux

Which llama.cpp modules do you know to be affected?

Other (Please specify in the next section)

Problem description & steps to reproduce

image
Run cd examples/server/tests
cd examples/server/tests
$env:PYTHONIOENCODING = ":replace"
pytest -v -x
shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
env:
LLAMA_LOG_COLORS: 1
LLAMA_LOG_PREFIX: 1
LLAMA_LOG_TIMESTAMPS: 1
LLAMA_LOG_VERBOSITY: 10
pythonLocation: C:\hostedtoolcache\windows\Python\3.11.9\x64
PKG_CONFIG_PATH: C:\hostedtoolcache\windows\Python\3.11.9\x64/lib/pkgconfig
Python_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.11.9\x64
Python2_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.11.9\x64
Python3_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.11.9\x64
pytest: D:\a_temp\4cf99d7f-0c62-442d-b9b9-7b88a28fd6b6.ps1:4
Line |
4 | pytest -v -x
| ~~~~~~
| The term 'pytest' is not recognized as a name of a cmdlet, function, script file, or executable program. Check
| the spelling of the name, or if a path was included, verify that the path is correct and try again.
Error: Process completed with exit code 1.

First Bad Commit

No response

Relevant log output

No response

@leo-pony
Copy link
Contributor Author

After rebase to ggerganov/master branch, this issue disappeared.

@leo-pony
Copy link
Contributor Author

After rebase to ggerganov/master branch, this issue disappeared.

With above rebase, issue resolved, close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant