Skip to content

[libc++] Run additional LLDB data formatters tests as part of libc++'s CI #110570

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

ldionne
Copy link
Member

@ldionne ldionne commented Sep 30, 2024

No description provided.

@ldionne ldionne requested a review from a team as a code owner September 30, 2024 20:57
@llvmbot llvmbot added the libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. label Sep 30, 2024
@llvmbot
Copy link
Member

llvmbot commented Sep 30, 2024

@llvm/pr-subscribers-libcxx

Author: Louis Dionne (ldionne)

Changes

Full diff: https://github.com/llvm/llvm-project/pull/110570.diff

1 Files Affected:

  • (modified) libcxx/utils/ci/run-buildbot (+8-1)
diff --git a/libcxx/utils/ci/run-buildbot b/libcxx/utils/ci/run-buildbot
index b0533cb9a49c93..1bd27eb344e8f7 100755
--- a/libcxx/utils/ci/run-buildbot
+++ b/libcxx/utils/ci/run-buildbot
@@ -371,7 +371,14 @@ bootstrapping-build)
           -DLLVM_LIT_ARGS="-sv --xunit-xml-output test-results.xml --timeout=1500 --time-tests"
 
     echo "+++ Running the LLDB libc++ data formatter tests"
-    ${NINJA} -vC "${BUILD_DIR}" check-lldb-api-functionalities-data-formatter-data-formatter-stl-libcxx
+    ${NINJA} -vC "${BUILD_DIR}" check-lldb-api-functionalities-data-formatter-data-formatter-stl-libcxx \
+                                check-lldb-api-functionalities-data-formatter-data-formatter-stl-generic \
+                                check-lldb-api-functionalities-data-formatter-data-formatter-stl-libcxx-simulators \
+                                check-lldb-api-commands-expression-import-std-module \
+                                check-lldb-api-lang-cpp-std-function-step-into-callable \
+                                check-lldb-api-lang-cpp-std-function-recognizer \
+                                check-lldb-api-lang-cpp-std-invoke-recognizer
+
 
     echo "--- Running the libc++ and libc++abi tests"
     ${NINJA} -vC "${BUILD_DIR}" check-runtimes

@ldionne
Copy link
Member Author

ldionne commented Sep 30, 2024

@Michael137 Otherwise, would it make sense to define a target in LLDB that would build all the tests that are relevant for libc++ integration? We could just build that target and you folks can add things to it when needed.

@Michael137
Copy link
Member

Thanks for the quick change!

Otherwise, would it make sense to define a target in LLDB that would build all the tests that are relevant for libc++ integration? We could just build that target and you folks can add things to it when needed.

I think that's a great idea. How about we land this change to get some immediate extra coverage and I'll open an issue on me to consolidate these into a single target?

@Michael137
Copy link
Member

Expectedly the GenericOptional LLDB test failed:

  lldb-api :: functionalities/data-formatter/data-formatter-stl/generic/optional/TestDataFormatterGenericOptional.py

Which is good. That means we got extra coverage

@ldionne
Copy link
Member Author

ldionne commented Oct 1, 2024

Merging despite the CI failure since the test that broke is exactly the one that we fixed by reverting #110355.

@ldionne ldionne merged commit d6d3d2f into llvm:main Oct 1, 2024
63 of 64 checks passed
@ldionne ldionne deleted the review/ci-additional-lldb-tests branch October 1, 2024 13:49
@Michael137
Copy link
Member

FYI, trying to add the consolidated target here: #110856

Sterling-Augustine pushed a commit to Sterling-Augustine/llvm-project that referenced this pull request Oct 3, 2024
Michael137 added a commit that referenced this pull request Oct 8, 2024
…0856)

We've been increasing the coverage of libc++ LLDB tests in the pre-merge
CI (see #110570). Unfortunately
the tests are spread across different targets. It would be great if we
had a single target that libc++ maintainers could run.

We do this by passing the `libc++` test-category as a parameter to
LLDB's [`dotest` testing
framework](https://lldb.llvm.org/resources/test.html). This will only
run LLDB tests that have been marked as belonging to the `libc++`
category.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants