Skip to content

[CI] LLDB should be tested on Clang changes in pre-merge CI #132795

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

Open
Endilll opened this issue Mar 24, 2025 · 2 comments
Open

[CI] LLDB should be tested on Clang changes in pre-merge CI #132795

Endilll opened this issue Mar 24, 2025 · 2 comments
Labels
clang Clang issues not falling into any other category infrastructure Bugs about LLVM infrastructure lldb

Comments

@Endilll
Copy link
Contributor

Endilll commented Mar 24, 2025

This was extensively discussed in #94208, and the outcome, highlighted in #94208 (comment), says that LLDB should be built and tested on changes to Clang. Unfortunately, back then we lacked the capacity to do that, which resulted in #95537.

This issue is filed mostly for bookkeeping purposes. It seems that we still don't have the capacity for this, so no immediate action is available.

@Endilll Endilll added clang Clang issues not falling into any other category infrastructure Bugs about LLVM infrastructure lldb labels Mar 24, 2025
@llvmbot
Copy link
Member

llvmbot commented Mar 24, 2025

@llvm/issue-subscribers-lldb

Author: Vlad Serebrennikov (Endilll)

This was extensively discussed in #94208, and the outcome, highlighted in https://github.com//pull/94208#issuecomment-2150706793, says that LLDB should be built and tested on changes to Clang. Unfortunately, back then we lacked the capacity to do that, which resulted in #95537.

This issue is filed mostly for bookkeeping purposes. It seems that we still don't have the capacity for this, so no immediate action is available.

@llvmbot
Copy link
Member

llvmbot commented Mar 24, 2025

@llvm/issue-subscribers-infrastructure

Author: Vlad Serebrennikov (Endilll)

This was extensively discussed in #94208, and the outcome, highlighted in https://github.com//pull/94208#issuecomment-2150706793, says that LLDB should be built and tested on changes to Clang. Unfortunately, back then we lacked the capacity to do that, which resulted in #95537.

This issue is filed mostly for bookkeeping purposes. It seems that we still don't have the capacity for this, so no immediate action is available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang Clang issues not falling into any other category infrastructure Bugs about LLVM infrastructure lldb
Projects
None yet
Development

No branches or pull requests

2 participants