| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I40f12ea1c90ecfc62a33de702121ec238f5e854d
|
|
Now using the version that's
present in the bionic images.
Meaning we have more warnings
but can also set the minimum
level to ignore a lot of them.
Fix the check for whether
shellcheck supports --severity.
(we have pipefail on, but we
expect shellcheck to fail in
this case)
Change-Id: I296b8554591b7d327c75393e3924184abc6512b7
|
|
First round of low hanging fruit
from the files with the fewest
warnings.
Change-Id: I60ad57b5bfb2f0be9bb6506252c820f44d055200
|
|
The previous commit makes use of $prefix, leading to
./jenkins-scripts/docker-run.sh: line 18: prefix: unbound variable
when the script is invoked without the --prefix option.
Change-Id: I92fb4f852b2fca7f9034bd7f43aa9b6663e4291b
|
|
functions when --prefix is given.
Change-Id: Icf7d3227d4b1b74e610d695b83f2202b84400152
|
|
Change-Id: If6f5d03352dd72d4a9e7345950efd65ae7f83eb0
|
|
flock expects a real command as argument, not a shell function, so the
scripts are currently broken:
flock: failed to execute container_exec: No such file or directory
This patch defines the JENKINS_FLOCK helper variable which is expanded
by the remote_exec() shell helper.
Change-Id: Ie5117d1116c9bbc9b556bc25946a7a0afc706ea2
|
|
In order to be able to remove old workspaces, this patch uses flock to
make sure the renaming for $dir to $dir.bak does not happen while a
build is in progress.
To achieve that, both the renaming and the command executed by
docker-run.sh use this exclusive lock.
Unfortunately, this does not prevent race conditions with builds not
relying on docker-run.sh, so such builds should either use flock or
switch to using docker-run.sh.
Change-Id: Ib8a7cbf33819d81f858c25f62a091b0b94c48d21
|
|
This patch updates tcwg_bmk-build.sh from the original copy of
tcwg_kernel-build.sh, and adds a couple minor changes to docker-run.sh
and tcwg-benchmark-results.sh.
tcwg-benchmark*: Switch results server to bkp-01.tcwglab
tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's build
round-robin.sh: Build LLVMgold.so plugin in build_llvm() for LTO
Change-Id: Ibde7a9d004c8b3328cdd36333c14574934b1eeab
|
|
Replace ${var:-default} with ${var-default}.
I learned something new about shell scripting today. From bash manual:
===
When not performing substring expansion, using the form described
below (e.g., ‘:-’), Bash tests for a parameter that is unset or null.
Omitting the colon results in a test only for a parameter that is
unset. Put another way, if the colon is included, the operator tests
for both parameter’s existence and that its value is not null; if
the colon is omitted, the operator tests only for existence.
===
The immediate problem I need to fix is handling of
host_aarchXX_excludecheck and host_x86_64_excludecheck parameters
in tcwg-buildfarm.sh. With ":-" syntax the empty ("null") values are
replaced by defaults, causing GCC testsuite to be ignored on aarchXX
hosts when "--host_aarchXX_excludecheck ''" is given.
There happens to be a single usage ":-" in ${rw:-rw} in
start-container-qemu.sh, where ":-" is actually needed.
Change-Id: Ibc8e070b698e1c76e2161eb65d40639b8cdec1f3
|
|
Change-Id: Ief6590b1b33df9d5de32d1cf070c4f37e01714c4
|
|
Change-Id: I6f3c27a50e2e737cf4d2dc332f994fb56e7e098f
|
|
When using "set -u" we get unbound variable failuer on empty arrays.
E.g., "set -u; arr=(); echo ${arr[@]}" will fail. We workaround by adding
"--" as first element to CONVERTED_ARGS and then referencing array as
"${CONVERTED_ARGS[@]:1}".
Change-Id: Id5304af6a0ead7da11d1799418acbb6abf3e1f71
|
|
Change-Id: I4d228bf828351be27b83c9086098ae4323829aaf
|
