feat(evaluations): add runtime evaluator#1286
Open
jstar0 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a
RuntimeEvaluatorfor comparing end-to-end wall-clock time across complete agent invocations. Run boundaries are retained on root agent data points, while open or incomplete runs are omitted instead of being reported as zero.The evaluator reuses the existing numerical aggregate result, so serialized evaluation output includes minimum, maximum, mean, median, mode, and standard deviation without introducing a visualizer-specific result type. Legacy session payloads without per-run boundaries remain supported.
Closes #1163
Type of change
Checklist
ruff check . && ruff format .)pytest tests)Verification
pytest -q packages/railtracks/tests/unit_tests/evaluations packages/railtracks/tests/integration_tests/evaluationsruff check . --no-fixruff format --check .mkdocs build --strictNotes
Runtime is recorded once for each run's root agent so nested agents do not duplicate a flow-level measurement. Failed runs with complete timing boundaries remain measurable; open and malformed runs are skipped.