Started 15 days ago
Took 5 hr 33 min

Unstable Build #1556 (May 19, 2020 7:32:26 PM)

Changes
  1. Add terminateCommands to lldb-vscode protocol (details)
  2. [analyzer] Change the default output type to PD_TEXT_MINIMAL in the frontend, error if an output loc is missing for PathDiagConsumers that need it (details)
  3. [analyzer][NFC][MallocChecker] Convert many parameters into CallEvent (details)
  4. [NFC] Add _EnableIfLValueCallable and move reference out of __callable. (details)
  5. Mark shared_ptr::__create_with_control_block as noexcept. (details)
  6. [NFC] Remove non-rvlaue non-variadic allocator::construct overloads. (details)
  7. [NFC] Remove non-rvlaue non-variadic allocator::construct overloads. (details)
  8. [analyzer][StackAddressEscape] Tie warnings to the diagnostic checkers rather then core.StackAddrEscapeBase (details)
  9. [mlir][ods] Fix ops with both attribute-sized operands and results (details)
  10. [mlir][Affine] Introduce affine memory interfaces (details)
  11. [mlir][vulkan-runner] Minor fix in timestamp flag for vulkan runner. (details)
  12. [DAGCombine] Remove the getNegatibleCost to avoid the out of sync with getNegatedExpression (details)
  13. [mlir][spirv] First step to support spirv cooperative matrix extension. (details)
  14. [mlir] NFC - Appease gcc 5 (details)
  15. AMDGPU/GlobalISel: Fix bug in test register bank (details)
  16. Mark AffineMap::replaceDimsAndSymbols as const (NFC) (details)
  17. [CGCall] Annotate references with "align" attribute. (details)
  18. [compiler-rt][scudo][LIT] Use target_suffix instead of target-arch (details)
  19. [mlir][SystemZ] Fix incompatible datalayout in SystemZ (details)
  20. [AMDGPU] Process V_MOV_B32_indirect in SET_GPR_IDX optimization (details)
  21. [Support][unittest] Fix HostTest.NumPhysicalCores on __i386__ after D78324 (details)
  22. [Test] Add missing auto-generated checks into tests (details)
  23. [NFC][PowerPC] Add 2 new cases to test livevars pass (details)

Started by upstream project LLDB Incremental build number 18776
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18777
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18781
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18782
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18783
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18784
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18787
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18788
originally caused by:

  • Started by timer
  • Started by timer

Started by upstream project LLDB Incremental build number 18790
originally caused by:

  • Started by timer
  • Started by timer

Started by upstream project LLDB Incremental build number 18791
originally caused by:

  • Started by timer
  • Started by timer

Started by upstream project LLDB Incremental build number 18792
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18793
originally caused by:

  • Started by timer

Started by upstream project LLDB Incremental build number 18795
originally caused by:

  • Started by timer

This run spent:

  • 9 hr 24 min waiting;
  • 5 hr 33 min build duration;
  • 11 hr total from scheduled to completion.
Revision: ea71685b0b17bb9197c5fe6cac5cb8fff2543847
  • refs/remotes/origin/master
Revision: 58684fbb6f2e6871f3f96ac8c7166a7d7486e971
  • refs/remotes/origin/master
Revision: ea71685b0b17bb9197c5fe6cac5cb8fff2543847
  • refs/remotes/origin/master
Test Result (1 failure / +1)
Revision: 6a075b6de4cafebec9ca1ff9eec7229a617c93f6
  • llvmorg-5.0.2
Revision: d0d8eb2e5415b8be29343e3c17a18e49e67b5551
  • llvmorg-7.0.1
Revision: 0399d5a9682b3cef71c653373e38890c63c4c365
  • llvmorg-9.0.0

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