Skip to content
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

Better classify what LLVM subproject is causing problems #579

Open
kwk opened this issue Jul 4, 2024 · 0 comments
Open

Better classify what LLVM subproject is causing problems #579

kwk opened this issue Jul 4, 2024 · 0 comments
Labels
ci enhancement New feature or request python

Comments

@kwk
Copy link
Collaborator

kwk commented Jul 4, 2024

When we still had standalone builds it was easy to point your finger at an LLVM sub-project that broke a build. We would assign a label such as project/llvm or project/clang. At the moment we only assign project/llvm all the time. It would be nice if more specific labels can be added from a path of a broken compilation or test. For starters, simply taking the first bit of a path should give us the project.

@kwk kwk added enhancement New feature or request python ci labels Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci enhancement New feature or request python
Projects
None yet
Development

No branches or pull requests

1 participant