Age | Commit message (Collapse) | Author |
|
|
|
|
|
... i think this works anyway
|
|
ideally `trait Runner` describes whatever should have behavioral
differences when a task is run locally vs in conjunction with a remote
server. then everything consuming a `dyn Runner` will not need to
change. if i've done it right.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
new hosts
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
i dunno how the `and not exists` is going to work out over time,
probably need some kinda checkpointing so that i don't have to rule out
the entire build history for a host every time it asks for a new task
|
|
|
|
|
|
|
|
onward, `rustc --version`!!
|
|
|
|
|
|
BETWEEN x86 AND aarch64
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
task_info kind overwrites the containing clientproto kind
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from invalid bounds
|
|
|