Skip to content

fix: resolve BitNet perplexity defaults from the script dir#475

Open
Gujiassh wants to merge 2 commits intomicrosoft:mainfrom
Gujiassh:fix/perplexity-default-paths
Open

fix: resolve BitNet perplexity defaults from the script dir#475
Gujiassh wants to merge 2 commits intomicrosoft:mainfrom
Gujiassh:fix/perplexity-default-paths

Conversation

@Gujiassh
Copy link
Copy Markdown

Summary

  • resolve the built-in llama-perplexity, llama-quantize, and data defaults in utils/test_perplexity.py relative to the script location instead of the caller's cwd
  • keep explicit user-supplied paths unchanged
  • add focused regression coverage for the default-path resolver and the PerplexityTester initialization path

Validation

  • python3 -m py_compile utils/test_perplexity.py tests/test_test_perplexity_paths.py
  • python3 -m unittest tests.test_test_perplexity_paths

Notes

  • this follow-up stays independent from #473 and #474, which already cover setup_env.py and utils/e2e_benchmark.py

Keep the perplexity utility usable from the repo root by resolving its built-in binary/data defaults relative to the script instead of the caller's cwd.

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
@Gujiassh
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

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

Successfully merging this pull request may close these issues.

1 participant