Started 2 mo 2 days ago
Took 10 hr on green-dragon-14

Failed Build #6603 (Sep 20, 2019 3:55:04 AM)


Git (git http://labmaster3.local/git/llvm-project.git)

  1. Fix for stringized function-macro args continued across lines (detail)
  2. [Consumed] Treat by-value class arguments as consuming by default, like (detail)
  3. MachineScheduler: Fix missing dependency with multiple subreg defs (detail)
  4. [NFCI] Always initialize const members of AttributeCommonInfo (detail)
  5. Revert "Fix swig python package path" (detail)
  6. [X86] Remove the special isBuildVectorOfConstantSDNodes handling from (detail)
  7. Use getTargetConstant for BLENDI, and add a test to catch it. (detail)
  8. llvm-undname: Delete an empty, unused method. (detail)
  9. Finish building the full-expression for a static_assert expression (detail)
  10. [Object] Uncapitalize an error message (detail)
  11. [llvm-ar] Removes repetition in the error message (detail)
  12. [X86] Use timm in MMX pinsrw/pextrw isel patterns. Add missing test (detail)
  13. [llvm-readobj] flush output before crash (detail)
  14. [X86] Convert tbm_bextri_u32/tbm_bextri_u64 intrinsics TargetConstant (detail)
  15. Reapply [llvm-ar] Include a line number when failing to parse an MRI (detail)
  16. [CallSiteSplitting] Remove unused includes (NFC). (detail)
  17. [MachinePipeliner] Improve the TargetInstrInfo API (detail)
  18. [yaml2obj/obj2yaml] - Do not trigger llvm_unreachable when (detail)
  19. [llvm-dwarfdump] Adjust Windows path to be acceptable by JSON (detail)

Started by upstream project clang-stage2-cmake-RgSan_relay build number 1320
originally caused by:

This run spent:

  • 2 ms waiting;
  • 10 hr build duration;
  • 10 hr total from scheduled to completion.
Revision: 9120829063de1885b88a1e274e17026552bbab68
  • detached
Revision: 447a47d472e9ad0a529c0920a0db6231506d3e91
  • refs/remotes/origin/master
Test Result (5 failures / +5)

Identified problems

Ninja target failed

Below is a link to the first failed ninja target.
Indication 1

Regression test failed

This build failed because a regression test in the test suite FAILed. See the test report for details.
Indication 2

Compile Error

This build failed because of a compile error. Below is a list of all errors in the build log:
Indication 3