Started 1 mo 13 days ago
Took 12 hr on green-dragon-09

Failed Build #6879 (Jan 10, 2020 8:06:57 AM)


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

  1. fix a few typos to cycle the bots (detail)
  2. fix another typo to cycle bots (detail)
  3. [ThinLTO] Pass CodeGenOpts like UnrollLoops/VectorizeLoop/VectorizeSLP (detail)
  4. [xray] Remove cl::sub from alias options (detail)
  5. clang-tidy doc - remove the widths (detail)
  6. [Syntax] Update comment, remove stale FIXME. NFC (detail)
  7. [LV] VPValues for memory operation pointers (NFCI) (detail)
  8. Restore order in clang-tidy section of release notes (detail)
  9. Allow system header to provide their own implementation of some builtin (detail)
  10. [NFC] [PowerPC] Add isPredicable for basic instrs (detail)
  11. [clangd] Improve type printing in hover (detail)
  12. [clangd] Fix markdown rendering in VSCode (detail)
  13. Fix several issues with compiler extensions (detail)
  14. [SVEV] Recognise hardware-loop intrinsic loop.decrement.reg (detail)
  15. Follow up of 67bf9a6154d4b82c, minor fix in test case, removed duplicate (detail)
  16. [libcxx] Force-cache LIBCXX_CXX_ABI_LIBRARY_PATH (detail)
  17. [CMake] Support running libc++abi tests in CrossWinToARMLinux cache file (detail)
  18. XFAIL load_extension.ll test on macOS only (detail)
  19. [MIR] Fix cyclic dependency of MIR formatter (detail)
  20. [LV] Silence unused variable warning in Release builds. NFC. (detail)
  21. Don't use dyn_cast_or_null if we know the pointer is nonnull. (detail)
  22. [X86][AVX] Add tests for v8f32/v8i32 089abcde and 0189abcd shuffles (detail)
  23. Fix Wdocumentation warning. NFCI. (detail)
  24. Fix Wdocumentation warning. NFCI. (detail)
  25. Data formatters: Look through array element typedefs (detail)
  26. Fix "pointer is null" static analyzer warnings. NFCI. (detail)
  27. [ARM,MVE] Make `vqrshrun` generate the right instruction. (detail)
  28. [ARM][Thumb2] Fix ADD/SUB invalid writes to SP (detail)
  29. [lldb/lua] Make convenience_variables.test compatible with lua-5.1 (detail)
  30. [lldb/DWARF] Don't automatically search dwo unit attributes (detail)
  31. [CodeComplete] Suggest 'return nullptr' in functions returning pointers (detail)
  32. [lldb] Surpress "bitfield too small" gcc warning (detail)
  33. [Support] ThreadPoolExecutor fixes for Windows/MinGW (detail)
  34. [lldb][tests] Take into account all parent's categories when traverse (detail)
  35. [lldb][test] NFC, re-use _getTestPath() function (detail)
  36. [FPEnv] Generate constrained FP comparisons from clang (detail)
  37. [lldb][tests] Cleanup '.categories' (detail)
  38. Reverting, broke some bots. Need further investigation. (detail)
  39. Sprinkle some constexpr on default ctors so the compiler can diagnose (detail)
  40. ARMLowOverheadLoops: a few more dbg msgs to better trace rejected TP (detail)
  41. RangeDataVector: Support custom sorting for D63540 (detail)
  42. [ARM][MVE] Tail predicate VMAX,VMAXA,VMIN,VMINA (detail)
  43. [FPEnv] Invert sense of MIFlag::FPExcept flag (detail)
  44. [lldb][tests][NFC] Unify variable naming convention (detail)
  45. [lldb][tests] Make it possible to expect failure for a whole category (detail)
  46. AMDGPU/GlobalISel: Clamp G_ZEXT source sizes (detail)
  47. [LIBOMPTARGET]Ignore empty target descriptors. (detail)
  48. [DebugInfo] Improve error message text (detail)
  49. [DebugInfo][NFC] Remove unused variable/fix variable naming (detail)

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

This run spent:

  • 1 ms waiting;
  • 12 hr build duration;
  • 12 hr total from scheduled to completion.
Revision: 7e02406f6cf180a8c89ce64665660e7cc9dbc23e
  • detached
Revision: 66f206567090b1d6e4879775d8308d3715379515
  • 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

Unexpected pass

This buildbot failed because a test marked as XFAIL unexpectedly passes. This could mean that the cause for the XFAIL is fixed, but it warrants investigation in any case.
Indication 2

Regression test failed

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

Compile Error

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