Task environment variable must be applied only on target process |
||
Issue descriptionRight now _run_manifest() in https://github.com/luci/luci-py/blob/master/appengine/swarming/swarming_bot/bot_code/bot_main.py applies the task environment variable. This is totally incorrect, then environment variables must be applied to the target process as started by run_isolated.py, two process deep (there's task_runner.py in between). This means passing the environment dict down the two processes. This could be done via task_in_file as the environment variables could be long and could overflow the command line limit.
,
Nov 29 2017
,
Nov 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/luci/luci-py.git/+/f61b1c62d72cb6229df05266d2188bfac753ed97 commit f61b1c62d72cb6229df05266d2188bfac753ed97 Author: Marc-Antoine Ruel <maruel@chromium.org> Date: Wed Nov 29 18:48:23 2017 Fix regression in fc3c34e59202ee and bfab799cddab1 subprocess.Popen() throws on Windows if env is not purely str instances. When passing arguments via a json file instead of normal arguments, the argument values are unicode instances instead of str. R=iannucci@chromium.org Bug: 728874 , 786503 Change-Id: I3cb5c751557285eb487b7b5d2029ec222e602032 Reviewed-on: https://chromium-review.googlesource.com/796935 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Marc-Antoine Ruel <maruel@chromium.org> [modify] https://crrev.com/f61b1c62d72cb6229df05266d2188bfac753ed97/client/run_isolated.py |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Nov 28 2017