Repository navigation
feat(scripts): full 89-task run on Windows/WSL - #18
Merged
Merged
Conversation
rzhang569
marked this pull request as draft
October 7, 2026 19:29
Collaborator
Author
|
Moved to draft: the WSL steps (op.exe, GlobalProtect networking) haven't been run on a real machine yet. I'm setting up the Windows box today and will fix the doc from what actually happens, then mark it ready. |
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
2 participants
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.
Tooling for the plan's next step: run all 89 tasks once on x86, then pick a new dev slice from the results.
scripts/run_full.sh— all tasks, one trial each;resumecontinues an interrupted job and re-runs gateway failures (harbor jobs resume). A full run is 8–12 h, so it will get interrupted.scripts/export_trials.py— one CSV row per trial (outcome, turns, tokens, time), small enough to commit so the run can be analysed off the machine that ran it.scripts/env.sh— loads the gateway settings, resolving the key withopor, in WSL,op.exe. 1Password has no WSL integration andop runcan't launch Linux programs from there.run_task.sh, which ranop runagainst the.env.optemplate with its<item>placeholder and couldn't have worked.docs/setup-windows.mdwith memory sizing, the GlobalProtect/WSL networking fix, power settings and tmux.The WSL parts are untested until I set up the machine today; I'll fix the doc from what actually happens.