1282066 - when running with taskcluster_interactive=true, the script just ends and the docker container goes away

Status: RESOLVED DUPLICATE of bug 1282065

(Taskcluster :: General, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

this is no fun, I just want to get things setup to run tests manually and all I do is file more bugs in bugzilla!

when I run the script from the task:
https://tools.taskcluster.net/task-inspector/#N6sRh9xrSlafCdTTK5SXyA/

I end up with a bunch of output:
.
:
# Save the computed mozharness command to a binary which is useful
# for interactive mode.
echo -e "#!/usr/bin/env bash
cmd=\"python2.7 $WORKSPACE/${MOZHARNESS_SCRIPT} ${config_cmds} ${@} \${@}\"
echo \"Running: \${cmd}\"
exec \${cmd}" > ${mozharness_bin}
+ echo -e '#!/usr/bin/env bash
cmd="python2.7 /home/worker/workspace/mozharness/scripts/desktop_unittest.py  --config-file /home/worker/workspace/mozharness/configs/unittests/linux_unittest.py --config-file /home/worker/workspace/mozharness/configs/remove_executables.py --no-read-buildbot-config' --installer-url=https://queue.taskcluster.net/v1/task/Sj_o9rDzRzGhCw0Hd4Oq2g/artifacts/public/build/target.tar.bz2 --test-packages-url=https://queue.taskcluster.net/v1/task/Sj_o9rDzRzGhCw0Hd4Oq2g/artifacts/public/build/target.test_packages.json --mochitest-suite=mochitest-media --total-chunk=1 --this-chunk=1 '--download-symbols=ondemand ${@}"
echo "Running: ${cmd}"
exec ${cmd}'
chmod +x ${mozharness_bin}
+ chmod +x /home/worker/bin/run-mozharness

# In interactive mode, the user will be prompted with options for what to do.
if [ "$TASKCLUSTER_INTERACTIVE" != "true" ]; then
  # run the given mozharness script and configs, but pass the rest of the
  # arguments in from our own invocation
  ${mozharness_bin};
fi
+ '[' true '!=' true ']'
cleanup
+ cleanup
+ local rv=0
+ [[ -s /home/worker/.xsession-errors ]]
+ cp /home/worker/.xsession-errors /home/worker/artifacts/public/xsession-errors.log
+ '[' -n 34 ']'
+ '[' false == false ']'
+ kill 34
+ exit 0
root@jmaher-ThinkPad-X230:~/mozilla# 


notice that we run into the cleanup() routine right away.  This isn't useful at all.

Comment 1

[Andrew Halberstadt [:ahal]]

This is the correct behaviour for "TASKCLUSTER_INTERACTIVE" when running remotely. I guess the question is should "TASKCLUSTER_INTERACTIVE" work for the local case too, or should we get that "RUN_LOCALLY" thing working. I think this and bug 1282065 are more or less the same bug, I replied more in depth over there.

Comment 2

[Dustin J. Mitchell [:dustin] (he/him)]

I feel like the interactive / run-at-home / etc. stuff is all in a bit of disarray, with overlaps and gaps in functionality.  Can we elect someone to try to bring some sanity to this process, and maybe write up some .rst docs in-tree?

Comment 3

[Armen [:armenzg]]

Should we dupe against the other bug?

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

I am fine with a dup against the other bug, and also agree with :dustin regarding the need for someone to own at the very least a small sanity cleanup of all methods and some docs about how to use them.