summaryrefslogtreecommitdiffstats
path: root/test_build.sh
diff options
context:
space:
mode:
authorPatrick Georgi <pgeorgi@google.com>2020-10-28 17:29:38 +0100
committerPatrick Georgi <pgeorgi@google.com>2020-11-03 06:46:17 +0000
commit07edbb9af4f5b692717b52ad84cca0728472755d (patch)
treee23e0fbfeb72eea67d4914158213c1791c39639a /test_build.sh
parent8a9218bf56e9f76c57ce347721500b451d8d6fa0 (diff)
downloadflashrom-07edbb9af4f5b692717b52ad84cca0728472755d.tar.gz
flashrom-07edbb9af4f5b692717b52ad84cca0728472755d.tar.bz2
flashrom-07edbb9af4f5b692717b52ad84cca0728472755d.zip
test_build.sh: Move build test procedure to repository
Instead of hard coding the test procedure on qa.coreboot.org, allow running a script in the repo instead. The server is already adapted to do that, so once there's a test_build.sh file in the toplevel directory, it's run in place of the default operation. The content of this change mirrors the default operation exactly so should serve as a good starting point. The script is executed in an encapsulate[0] context with the workspace, /tmp and $HOME/.ccache writable, everything else read-only and network disabled. It should return 0 on success, anything else on failure, as is normal for UNIX processes. [0] https://review.coreboot.org/cgit/encapsulate.git Change-Id: I37a8e925d1b283c3b8f87cb3d0f1ed8920f2cf95 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/46894 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Edward O'Callaghan <quasisec@chromium.org>
Diffstat (limited to 'test_build.sh')
-rwxr-xr-xtest_build.sh8
1 files changed, 8 insertions, 0 deletions
diff --git a/test_build.sh b/test_build.sh
new file mode 100755
index 000000000..0e43cd353
--- /dev/null
+++ b/test_build.sh
@@ -0,0 +1,8 @@
+#!/bin/sh
+set -e
+
+make CONFIG_EVERYTHING=yes WARNERROR=yes
+
+meson out
+(cd out && ninja)
+(cd out && ninja test)