Currently these runvars are either URLs provided by the definition
(e.g. make-flight) or output controller-relative paths created by the
execution (in the case where they aren't from the definition).
This wierd dual-semantics is confusing and wrong, and in particular is
broken if the test step is
Ian Campbell writes ("[PATCH OSSTEST] ts-debian-di-install: Don't set runvars
for netboot kernel+ramdisk as outputs"):
> Currently these runvars are either URLs provided by the definition
> (e.g. make-flight) or output controller-relative paths created by the
> execution (in the case where they
