Maksym Taran

To see if anything goes wrong, etc.

IDENG-428TagsbugCreated byThomas BroadleyStatusNot startedSpeculativeGood starter taskE.g. 87199.I think this is related to the agent state or some other environment variable passed to mp4_functions.py being too large.

Make debug data from `waitFor()` a little easier to read

2

Separates it better from the waiting reason and pretty-prints it.

Support migrating runs from one viv instance to another

2

This is desired to make it easy to interoperate across multiple viv nodes. ## Plan - specify S3 buckets (import/export) via env vars - specify auth keys for S3 buckets...

Allow viv to start more runs while a GPU run is waiting for a VP machine

1

Currently if you try starting a run of a task that needs GPUs, it'll try to allocate a new VP machine and wait for that process to finish. This can...

Make viv cli support ssh to VP node containers

1

Currently viv ssh only supports connecting to runs/task envs on the primary vm host, not on VP nodes.

Support stop/restart workflow on multi-node

5

Nowadays human baselines run in a container on a VP machine, then the container is stopped, and eventually it's later restarted to score it and otherwise look at what was...

Document how to provision VP machine for multi-node

1

While there's not yet a fully-automatic way of provisioning a VP machine, there should be some documentation on how to add a VP machine.

Currently when a VP machine is being set up, it just looks like all the runs waiting for it are still just enqueued. It'd be better to show some indication...

[setupNoInternetSandboxing](https://github.com/METR/vivaria/blob/main/server/src/docker/VmHost.ts#L97) should apply to VP machines as well as the primary vm host. We can do this automatically, or include this in documentation for a manual process to provision VP...