Skip to content

Commit c900954

Browse files
authored
[libc++] Run the LLDB data formatter tests after libc++'s own tests (#119028)
It makes more sense to start testing libc++ with the latest compiler and only then to run the LLDB data formatter tests, since that provides more signal than starting with the data formatter tests.
1 parent ec27eb8 commit c900954

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

libcxx/utils/ci/run-buildbot

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -387,16 +387,16 @@ bootstrapping-build)
387387
-DLLVM_ENABLE_ASSERTIONS=ON \
388388
-DLLVM_LIT_ARGS="-sv --xunit-xml-output test-results.xml --timeout=1500 --time-tests"
389389

390-
step "Running the LLDB libc++ data formatter tests"
391-
${NINJA} -vC "${BUILD_DIR}" lldb-api-test-deps
392-
${BUILD_DIR}/bin/llvm-lit -sv --param dotest-args='--category libc++' "${MONOREPO_ROOT}/lldb/test/API"
393-
394390
step "Running the libc++ and libc++abi tests"
395391
${NINJA} -vC "${BUILD_DIR}" check-runtimes
396392

397393
step "Installing libc++ and libc++abi to a fake location"
398394
${NINJA} -vC "${BUILD_DIR}" install-runtimes
399395

396+
step "Running the LLDB libc++ data formatter tests"
397+
${NINJA} -vC "${BUILD_DIR}" lldb-api-test-deps
398+
${BUILD_DIR}/bin/llvm-lit -sv --param dotest-args='--category libc++' "${MONOREPO_ROOT}/lldb/test/API"
399+
400400
ccache -s
401401
;;
402402
generic-static)

0 commit comments

Comments
 (0)