note that becase the two calls to vm.MonitorOutput() do not share any state (offset they've last read from the output log file), in case there's an output present the user will see two identical outputs from that file, however, since tart run generally outputs only when something is really wrong, this shouldn't be an issue
nohuperror in https://github.com/cirruslabs/gitlab-tart-executor/issues/30#issuecomment-1636068414tart runprocess is holding GitLab Runner's file descriptors that we passed totart runin hostage (see https://github.com/golang/go/issues/23019)vm.MonitorOutput()do not share any state (offset they've last read from the output log file), in case there's an output present the user will see two identical outputs from that file, however, sincetart rungenerally outputs only when something is really wrong, this shouldn't be an issue