Skip to content

fix: use absolute paths in fle inspect-eval#363

Open
JackHopkins wants to merge 1 commit intomainfrom
fix/inspect-eval-absolute-paths
Open

fix: use absolute paths in fle inspect-eval#363
JackHopkins wants to merge 1 commit intomainfrom
fix/inspect-eval-absolute-paths

Conversation

@JackHopkins
Copy link
Copy Markdown
Owner

Summary

  • Resolve eval/inspect_integration/eval_set.py and agent_task.py paths using Path(__file__).parent instead of hardcoded relative paths, so fle inspect-eval works when run from any directory (not just the source repo root)
  • Fix bug where multiple --tasks values were joined into a single space-separated string argument instead of separate inspect eval arguments
  • Update help text examples to use ./solver_experiments.py instead of the old internal relative path

Test plan

  • cd /tmp && fle inspect-eval -h succeeds without errors
  • fle inspect-eval --tasks iron_plate_throughput --model openai/gpt-4o-mini --limit 1 prints command with absolute paths
  • fle inspect-eval --tasks task_a,task_b --model openai/gpt-4o-mini passes each task spec as a separate argument
  • --eval-set-file ./custom.py still resolves relative to CWD (not changed by this PR)

The `inspect eval` subprocess commands used hardcoded relative paths
like `eval/inspect_integration/eval_set.py@task_name`, which only
worked when run from the source repo root. This resolves the paths
relative to the installed package using `Path(__file__).parent`,
following the same pattern already used by `fle_cluster`.

Also fixes a bug where multiple `--tasks` were joined into a single
space-separated string argument instead of being passed as separate
arguments to `inspect eval`.
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