Started 2 mo 25 days ago
Took 2 hr 18 min

Failed Build #23771 (Sep 10, 2020 1:07:45 PM)

Changes
  1. [lldb] Have the Xcode build run check-lldb instead of just check-lldb-shell (details / githubweb)
Changes
  1. [Support] Use unique_function rather than std::function for ThreadPool TaskTy. (details)
  2. [NFC] Fix whitespace in lldb-vscode --help (details)
  3. [PGO] Skip if an IndirectBrInst critical edge cannot be split (details)
  4. [compiler-rt] [netbsd] Update generate_netbsd_syscalls.awk (details)
  5. [compiler-rt] [netbsd] Regenerate syscall hooks (details)
  6. [SLPVectorizer][X86][AMDGPU] Remove fcmp+select to fmin/fmax reduction support. (details)
  7. Revert "[Support] Use unique_function rather than std::function for ThreadPool TaskTy." (details)
  8. [WebAssembly] Set unreachable as canonical to permit disassembly (details)
  9. Make struct dialects have the same field name as everything else, 'dialect'. (details)
  10. Allow Dialects to be initialized via nullptr. (details)
  11. [gn build] (semi-manually) port 009cd4e4910 (details)
  12. Fix operator!= for Dialects. (details)
  13. [Hexagon] Split pair-based masked memops (details)
  14. [SVE] Bail from VectorUtils heuristics for scalable vectors (details)
  15. [ImplicitNullChecks] NFC: Remove unused PointerReg arg in dep analysis (details)
  16. [libc][NFC][obvious] Remove a redudant dep of strcmp implementation. (details)
  17. Diable sanitizer options for amdgpu (details)
  18. GlobalISel: Combine fneg(fneg x) to x (details)
Changes
  1. [lldb] Have the Xcode build run check-lldb instead of just check-lldb-shell (details)

Started by timer (15 times)

This run spent:

  • 2 hr 22 min waiting;
  • 2 hr 18 min build duration;
  • 4 hr 40 min total from scheduled to completion.
Revision: f63e49a069fad6631c55559cc9bdbb8e66dba34c
  • refs/remotes/origin/master
Revision: d4bf90271fa988101bdad4f2e78b8c3a0b85fc2d
  • refs/remotes/origin/master
Revision: f63e49a069fad6631c55559cc9bdbb8e66dba34c
  • refs/remotes/origin/master
Test Result (1 failure / +1)

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