chromium/src
0
Fork 0
Code Activity

Add link to public buildbots for clang packaging test failures

Browse Source 
Change-Id: I9dc5e6476b32543d1968db266b1eec9b1007597f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6369924
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Arthur Eubanks <aeubanks@google.com>
Cr-Commit-Position: refs/heads/main@{#1435471}
This commit is contained in:
Arthur Eubanks
2025-03-20 09:10:06 -07:00
committed by Chromium LUCI CQ
parent 3355588fab
commit c8399775cb
1 changed files with 12 additions and 0 deletions

12
docs/clang_gardening.md

@ -46,6 +46,18 @@ The gardener is also responsible for taking notes during the weekly Chrome toolc
[TOC]
## Clang packaging test failures
When packaging clang/LLVM on our various supported platforms (`upload_*_clang`
tryjobs), we run the entire LLVM test suite and block the build if any
test failed. The most common test failures we see are Mac and Windows-specific
tests since upstream LLVM is mostly Linux-focused. There are public bots that
also run LLVM tests, mostly accessible from https://lab.llvm.org/buildbot.
There are also some Apple bots running at
http://green.lab.llvm.org/job/llvm.org/ which mirror test failures we see on
Mac. Reverting the culprit change upstream with a pointer to a public bot
showing the test failure is encouraged.
## Disk out of space
If there are any issues with disk running out of space, file a go/bug-a-trooper