Started 2 mo 17 days ago
Took 4 hr 20 min

Unstable Build #2436 (Jan 30, 2021 12:38:03 PM)

Changes
  1. [ConstraintElimination] Verify CS and DFSInStack are in sync.(NFC) (details)
  2. [OpenMP][NVPTX] Refined CMake logic to choose compute capabilites (details)
  3. [TableGen] Avoid a couple vector copies in ExpandHwModeBasedTypes. (details)
  4. [TableGen] Use emplace_back to add to PatternsToMatch in GenerateVariants. Use std::move when adding to PatternsToMatch in AddPatternToMatch. (details)
  5. [RISCV] Use MVT instead of EVT in RISCVISelDAGToDAG.cpp (details)

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

  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer

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

  • Started by timer
  • Started by timer
  • Started by timer

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

  • Started by timer
  • Started by timer
  • Started by timer

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

  • Started by timer
  • Started by timer
  • Started by timer
  • Started by timer

This run spent:

  • 9 hr 22 min waiting;
  • 4 hr 20 min build duration;
  • 10 hr total from scheduled to completion.
Revision: 2d096eb6dc44781c7ecd1caf08c676f31857750b
  • refs/remotes/origin/main
Revision: 3fdf2a56dd00ece7b6572e592f40b207ef85f96f
  • refs/remotes/origin/main
Revision: 2d096eb6dc44781c7ecd1caf08c676f31857750b
  • refs/remotes/origin/main
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

Regression test failed

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

Ninja target failed

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

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 3