Started 3 mo 10 days ago
Took 2 hr 39 min

Build clang-d391384-gaa4685c0fb3a-t21719-b21719.tar.gz (Jun 17, 2021 1:26:08 PM)


No known issues detected

Build Log

  1. Add flang-x86_64-windows builder. (details / githubweb)
  1. test: clean up some of the RISCV tests (NFC) (details)
  2. [libcxx][iwyu] 🎨 adds more headers to IWYU (details)
  3. [libcxx][module-map] 🎨 updates module map to account for ranges headers (details)
  4. [mlir][sparse] Add Matricized Tensor Times Khatri-Rao Product (MTTKRP) integration test (details)
  5. [clang] Fix a race condition in the build of clangInterpreter (details)
  6. [lld-macho] Implement ICF (details)
  7. [gn build] Port f27e4548fc42 (details)
  8. [AIX] Remove --as-needed passing into aix linker (details)
  9. [NFC] LoopVectorizationCostModel::getMaximizedVFForTarget(): clarify debug msg (details)
  10. [X86] AMD Zen 3: don't confuse shift and shuffle, NFC (details)
  11. [llvm-symbolizer][docs] Update example for --verbose in the guide (details)
  12. [lld-macho] Rework mergeFlag to behave closer to what ld64 does. (details)
  13. [lld][WebAssembly] Add new `--import-undefined` option (details)
  14. [MCA] [RegisterFile] Allow for skipping Defs with RegID of 0 (rather than assert(RegID) like we do before this patch). (details)
  15. [LoopUnroll] Fold all exits based on known trip count/multiple (details)
  16. [lldb-vscode] only report long running progress events (details)

Started by upstream project relay-lnt-ctmark build number 12498
originally caused by:

This run spent:

  • 2 hr 35 min waiting;
  • 2 hr 39 min build duration;
  • 2 hr 39 min total from scheduled to completion.
Revision: c406b636839cf07367241c224da3c0207c1396a3
  • refs/remotes/origin/main
Revision: aa4685c0fb3aab5acb90be5fd3eb5ba8bf1e3211
Repository: http://labmaster3.local/git/llvm-project.git
  • detached
Revision: f48d431f44610e339d00a33d57564c6029c4ff43
  • refs/remotes/origin/main
Revision: 24550c3385e8e3703ed364e1ce20b06de97bbeee
  • refs/remotes/origin/main

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.