Mahmood Ali 058076afd0 client: stop using alloc.TaskResources ...

Now that alloc.Canonicalize() is called in all alloc sources in the
client (i.e. on state restore and RPC fetching), we no longer need to
check alloc.TaskResources.

alloc.AllocatedResources is always non-nil through alloc runner.
Though, early on, we check for alloc validity, so NewTaskRunner and
TaskEnv must still check.  `TestClient_AddAllocError` test validates
that behavior.

2020-01-09 09:25:07 -05:00

25 KiB

Raw Blame History

View Raw