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-cuda-l4, clang-cuda-p4, and clang-cuda-t4 are not reliable #215

Open
gkistanova opened this issue Jun 26, 2024 · 3 comments
Open

clang-cuda-l4, clang-cuda-p4, and clang-cuda-t4 are not reliable #215

gkistanova opened this issue Jun 26, 2024 · 3 comments
Assignees

Comments

@gkistanova
Copy link
Contributor

Here is the example of false negatives (when failure does not seem related to the commit a builder builds) from these 3 builders:

For the mean time I marked them silent (no failure reporting to blame lists or github).

gkistanova added a commit that referenced this issue Jun 26, 2024
…gative builds gets resolved.

See #215 for more details.
@fhahn
Copy link

fhahn commented Jun 28, 2024

Thanks!

@Artem-B
Copy link
Member

Artem-B commented Jul 8, 2024

Those would be libc-on-GPU tests. AFAICT the bots do report a real problem. The fact that the failure may be attributed to a wrong commit probably means that we didn't trigger the tests on all the changes relevant to libc, so the first commit to the LLVM or clang sources is the first to report the failure.

@jhuber6 : FYI. The libc on GPU tests are still broken, though in a different way.

@Artem-B Artem-B assigned jhuber6 and unassigned Artem-B Jul 8, 2024
@jhuber6
Copy link
Contributor

jhuber6 commented Jul 8, 2024

Can you link me to where the bot currently lives?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants