Browse Source

Fix error reporting in requirements.sh script

The 'echo %1' in requirements.sh did just that, echoed %1 without
reporting the source of the pip error. This patch changes this
command to 'cat $1', which dumps the content of the file referred
to by $1. This content is the pip package to install. Upon failure,
the user can know exactly which pip build failed and search for the
relevant error message in the build log.

Change-Id: Ieb5c928c31f1a6673152a0b1a15f6efe21cc063e
Chris Hoge 4 months ago
parent
commit
7fd814b15e
1 changed files with 1 additions and 1 deletions
  1. 1
    1
      scripts/requirements.sh

+ 1
- 1
scripts/requirements.sh View File

@@ -45,7 +45,7 @@ if [ ! -z "${PIP_PACKAGES}" ]; then
45 45
 fi
46 46
 
47 47
 echo uwsgi enum-compat ${PIP_PACKAGES} | xargs -n1 | split -l1 -a3
48
-ls -1 | xargs -n1 -P20 -t bash -c 'pip wheel ${PIP_WHEEL_ARGS} --no-deps --wheel-dir / -c /upper-constraints.txt -r $1 || echo %1 >> /failure' _ | tee /tmp/wheels.txt
48
+ls -1 | xargs -n1 -P20 -t bash -c 'pip wheel ${PIP_WHEEL_ARGS} --no-deps --wheel-dir / -c /upper-constraints.txt -r $1 || cat $1 >> /failure' _ | tee /tmp/wheels.txt
49 49
 
50 50
 # TODO: Improve the failure catching
51 51
 if [[ -f /failure ]]; then

Loading…
Cancel
Save