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

clang-format job on Buildkite is bogus #66468

Closed
asl opened this issue Sep 15, 2023 · 7 comments · Fixed by #66649
Closed

clang-format job on Buildkite is bogus #66468

asl opened this issue Sep 15, 2023 · 7 comments · Fixed by #66649
Assignees
Labels
bug Indicates an unexpected problem or unintended behavior infrastructure Bugs about LLVM infrastructure

Comments

@asl
Copy link
Collaborator

asl commented Sep 15, 2023

Consider e.g. https://buildkite.com/llvm-project/clang-ci/builds/3190#018a97ac-63f5-4517-ae31-3f185df940ae
clang-format job failed, however, there is no way to figure out what is wrong: the output is simply missed from the log.

@asl asl added bug Indicates an unexpected problem or unintended behavior infrastructure Bugs about LLVM infrastructure labels Sep 15, 2023
@llvmbot
Copy link
Collaborator

llvmbot commented Sep 15, 2023

@llvm/issue-subscribers-bug

Consider e.g. https://buildkite.com/llvm-project/clang-ci/builds/3190#018a97ac-63f5-4517-ae31-3f185df940ae clang-format job failed, however, there is no way to figure out what is wrong: the output is simply missed from the log.

@llvmbot
Copy link
Collaborator

llvmbot commented Sep 15, 2023

@llvm/issue-subscribers-infrastructure

Consider e.g. https://buildkite.com/llvm-project/clang-ci/builds/3190#018a97ac-63f5-4517-ae31-3f185df940ae clang-format job failed, however, there is no way to figure out what is wrong: the output is simply missed from the log.

@owenca owenca added libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. and removed clang-format labels Sep 15, 2023
@metaflow metaflow assigned ldionne and unassigned metaflow Sep 15, 2023
@metaflow
Copy link
Contributor

@ldionne could you please take a look?

@Endilll Endilll removed the new issue label Sep 15, 2023
ldionne added a commit to ldionne/llvm-project that referenced this issue Sep 15, 2023
Instead of using the BuildKite jobs, use GitHub actions to detect
clang-format violations and trailing whitespace in PRs.

Fixes llvm#66468
@ldionne ldionne assigned tru and unassigned ldionne Sep 15, 2023
@ldionne
Copy link
Member

ldionne commented Sep 15, 2023

Actually, I'll assign this to @tru since he's made a lot of progress on setting up clang-format for the whole monorepo. That will replace the Buildkite job we have for Clang.

@asl
Copy link
Collaborator Author

asl commented Sep 15, 2023

Will you please disable the job now as it simply makes everything else fail?

@asl asl removed the libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. label Sep 15, 2023
@ldionne
Copy link
Member

ldionne commented Sep 15, 2023

a52560c

The issue is that someone (you?) added trailing whitespace. The job output isn't great, but it does say:

grep -rnI '[[:blank:]] clang/lib clang/include clang/docs
clang/lib/CodeGen/CGCoroutine.cpp:836:

@asl
Copy link
Collaborator Author

asl commented Sep 15, 2023

grep -rnI '[[:blank:]] clang/lib clang/include clang/docs
clang/lib/CodeGen/CGCoroutine.cpp:836:

And how one could deduce that this is something related to the failure? And not just some part of job script? Especially given that line 69 is absent from the log and one could clearly expect to see the error there (after ":" on the line above). Certainly, it is clear what is going on to whoever written this script, but for everyone else the output is very confusing. I spent quite some time trying to find the error message in various parts of the system including raw logs, etc.

That said, is it possible to annotate steps somehow? Is it possible to provide some error messages instead of just user command error: exit status 1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior infrastructure Bugs about LLVM infrastructure
Projects
None yet
7 participants