summaryrefslogtreecommitdiff
path: root/.azure-pipelines.yml
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2023-10-26 14:31:38 -0400
committerTom Rini <trini@konsulko.com>2023-11-07 14:49:40 -0500
commit56ea7c8b7534d676120b37f70427724a1e0965e2 (patch)
tree30b25923b3db8254012d44cfb8cc877dfccdedff /.azure-pipelines.yml
parent703b5b33cd11ee55dc7196a750666ed773c412cf (diff)
downloadu-boot-56ea7c8b7534d676120b37f70427724a1e0965e2.tar.gz
u-boot-56ea7c8b7534d676120b37f70427724a1e0965e2.tar.bz2
u-boot-56ea7c8b7534d676120b37f70427724a1e0965e2.zip
CI, pytest: Add a test for sandbox without LTO
The primary motivation for having a sandbox without LTO build in CI is to ensure that we don't have that option break. We now have the ability to run tests of specific options being enabled/disabled, so drop the parts of CI that build and test that configuration specifically and add a build test instead. We still test that "NO_LTO=1" rather than editing the config file works via the ftrace tests. Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to '.azure-pipelines.yml')
-rw-r--r--.azure-pipelines.yml3
1 files changed, 0 insertions, 3 deletions
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index d6f3fa423c..b9d6aa98a0 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -287,9 +287,6 @@ stages:
sandbox64_clang:
TEST_PY_BD: "sandbox64"
OVERRIDE: "-O clang-16"
- sandbox_nolto:
- TEST_PY_BD: "sandbox"
- BUILD_ENV: "NO_LTO=1"
sandbox_spl:
TEST_PY_BD: "sandbox_spl"
TEST_PY_TEST_SPEC: "test_ofplatdata or test_handoff or test_spl"