phoenix-oss/llama-stack-mirror

mirror of https://github.com/meta-llama/llama-stack.git synced 2025-06-27 18:50:41 +00:00

History

Sumit Jaiswal 90d03552d4 Some checks failed Integration Tests / test-matrix (http, 3.10, agents) (push) Failing after 4s Details Integration Auth Tests / test-matrix (oauth2_token) (push) Failing after 8s Details Integration Tests / test-matrix (http, 3.10, inference) (push) Failing after 8s Details Integration Tests / test-matrix (http, 3.10, tool_runtime) (push) Failing after 6s Details Integration Tests / test-matrix (http, 3.10, vector_io) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.10, inspect) (push) Failing after 9s Details Integration Tests / test-matrix (http, 3.11, providers) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.10, post_training) (push) Failing after 13s Details Integration Tests / test-matrix (http, 3.11, tool_runtime) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.10, scoring) (push) Failing after 11s Details Integration Tests / test-matrix (http, 3.11, post_training) (push) Failing after 5s Details Integration Tests / test-matrix (http, 3.10, providers) (push) Failing after 8s Details Integration Tests / test-matrix (http, 3.12, datasets) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.11, agents) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.11, scoring) (push) Failing after 11s Details Integration Tests / test-matrix (http, 3.11, inference) (push) Failing after 9s Details Integration Tests / test-matrix (http, 3.12, post_training) (push) Failing after 7s Details Integration Tests / test-matrix (http, 3.12, agents) (push) Failing after 11s Details Integration Tests / test-matrix (http, 3.12, scoring) (push) Failing after 9s Details Integration Tests / test-matrix (http, 3.10, datasets) (push) Failing after 12s Details Integration Tests / test-matrix (http, 3.12, inference) (push) Failing after 10s Details Integration Tests / test-matrix (http, 3.11, inspect) (push) Failing after 9s Details Integration Tests / test-matrix (http, 3.11, datasets) (push) Failing after 11s Details Integration Tests / test-matrix (http, 3.12, providers) (push) Failing after 11s Details Integration Tests / test-matrix (http, 3.11, vector_io) (push) Failing after 8s Details Integration Tests / test-matrix (http, 3.12, inspect) (push) Failing after 8s Details Integration Tests / test-matrix (http, 3.12, vector_io) (push) Failing after 8s Details Integration Tests / test-matrix (library, 3.10, agents) (push) Failing after 12s Details Integration Tests / test-matrix (http, 3.12, tool_runtime) (push) Failing after 8s Details Integration Tests / test-matrix (library, 3.10, post_training) (push) Failing after 7s Details Integration Tests / test-matrix (library, 3.10, datasets) (push) Failing after 12s Details Integration Tests / test-matrix (library, 3.10, inspect) (push) Failing after 10s Details Integration Tests / test-matrix (library, 3.10, providers) (push) Failing after 8s Details Integration Tests / test-matrix (library, 3.10, tool_runtime) (push) Failing after 7s Details Integration Tests / test-matrix (library, 3.10, scoring) (push) Failing after 7s Details Integration Tests / test-matrix (library, 3.10, vector_io) (push) Failing after 13s Details Integration Tests / test-matrix (library, 3.10, inference) (push) Failing after 7s Details Integration Tests / test-matrix (library, 3.11, agents) (push) Failing after 11s Details Integration Tests / test-matrix (library, 3.11, inference) (push) Failing after 10s Details Integration Tests / test-matrix (library, 3.11, inspect) (push) Failing after 7s Details Integration Tests / test-matrix (library, 3.11, datasets) (push) Failing after 11s Details Integration Tests / test-matrix (library, 3.11, post_training) (push) Failing after 5s Details Integration Tests / test-matrix (library, 3.11, providers) (push) Failing after 5s Details Integration Tests / test-matrix (library, 3.11, scoring) (push) Failing after 5s Details Integration Tests / test-matrix (library, 3.11, tool_runtime) (push) Failing after 4s Details Integration Tests / test-matrix (library, 3.11, vector_io) (push) Failing after 5s Details Integration Tests / test-matrix (library, 3.12, agents) (push) Failing after 4s Details Integration Tests / test-matrix (library, 3.12, datasets) (push) Failing after 6s Details Integration Tests / test-matrix (library, 3.12, inspect) (push) Failing after 4s Details Integration Tests / test-matrix (library, 3.12, inference) (push) Failing after 6s Details Integration Tests / test-matrix (library, 3.12, post_training) (push) Failing after 4s Details Integration Tests / test-matrix (library, 3.12, providers) (push) Failing after 11s Details Integration Tests / test-matrix (library, 3.12, scoring) (push) Failing after 11s Details Integration Tests / test-matrix (library, 3.12, tool_runtime) (push) Failing after 9s Details Integration Tests / test-matrix (library, 3.12, vector_io) (push) Failing after 7s Details Test External Providers / test-external-providers (venv) (push) Failing after 1m1s Details Unit Tests / unit-tests (3.11) (push) Failing after 1m11s Details Unit Tests / unit-tests (3.10) (push) Failing after 1m13s Details Unit Tests / unit-tests (3.12) (push) Failing after 1m9s Details Unit Tests / unit-tests (3.13) (push) Failing after 15s Details Pre-commit / pre-commit (push) Successful in 1m52s Details feat: To add health check for faiss inline vector_io provider (#2319 ) # What does this PR do? <!-- Provide a short summary of what this PR does and why. Link to relevant issues if applicable. --> To add health check for faiss inline vector_io provider. I tried adding `async def health(self) -> HealthResponse:` like in inference provider, but it didn't worked for `inline->vector_io->faiss` provider. And via debug logs, I understood the critical issue, that the health responses are being stored with the API name as the key, not as a nested dictionary with provider IDs. This means that all providers of the same API type (e.g., "vector_io") will share the same health response, and only the last one processed will be visible in the API response. I've created a patch file that fixes this issue by: - Storing the original get_providers_health method - Creating a patched version that correctly maps health responses to providers - Applying the patch to the `ProviderImpl` class Not an expert, so please let me know, if there can be any other workaround using which I can get the health status updated directly from `faiss.py`. <!-- If resolving an issue, uncomment and update the line below --> <!-- Closes #[issue-number] --> ## Test Plan <!-- Describe the tests you ran to verify your changes with result summaries. Provide clear instructions so the plan can be easily re-executed. --> Added unit tests to test the provider patch implementation in the PR. Adding a screenshot with the FAISS inline vector_io health status as "OK" ![faiss_health_check](https://github.com/user-attachments/assets/d769e762-890c-41ea-a596-5e90951f79a4)		2025-06-18 17:56:25 +02:00
..
client-sdk/post_training	feat: Add nemo customizer (#1448 )	2025-03-25 11:01:10 -07:00
common	feat(responses): implement full multi-turn support (#2295 )	2025-06-02 15:35:49 -07:00
external-provider/llama-stack-provider-ollama	chore: mark blobpath as optional (#2271 )	2025-05-27 10:55:24 +02:00
integration	feat: Add `suffix` to openai_completions (#2449 )	2025-06-13 16:06:06 -07:00
unit	feat: To add health check for faiss inline vector_io provider (#2319 )	2025-06-18 17:56:25 +02:00
verifications	feat: File search tool for Responses API (#2426 )	2025-06-13 14:32:48 -04:00
__init__.py	refactor(test): introduce --stack-config and simplify options (#1404 )	2025-03-05 17:02:02 -08:00
Containerfile	ci: use ollama container image with loaded models (#2410 )	2025-06-06 12:08:20 +02:00
README.md	docs: revamp testing documentation (#2155 )	2025-05-13 11:28:29 -07:00

README.md

Llama Stack Tests

Llama Stack has multiple layers of testing done to ensure continuous functionality and prevent regressions to the codebase.

Testing Type	Details
Unit	unit/README.md
Integration	integration/README.md
Verification	verifications/README.md