Started 23 days ago
Took 2 hr 9 min

Failed Build #24025 (Sep 30, 2020 10:01:11 AM)

Changes
  1. [zorg] [PowerPC] Limit number of threads to 64 on clang-ppc64le-rhel buildbot (details / githubweb)
Changes
  1. [FE] Use preferred alignment instead of ABI alignment for complete object when applicable (details)
  2. [mlir][Linalg] Generalize the logic to compute reassociation maps (details)
  3. [InstCombine] Add bswap(trunc(bswap(x))) -> trunc(lshr(x, c)) vector tests (details)
  4. [InstCombine] Fix bswap(trunc(bswap(x))) -> trunc(lshr(x, c)) vector support (details)
  5. [PowerPC] Avoid unused variable warning in Release builds (details)
  6. [PPC] Do not emit extswsli in 32BIT mode when using -mcpu=pwr9 (details)
  7. [InstCombine] Add tests for 'partial' bswap patterns (details)
  8. [NFC][regalloc] Make VirtRegAuxInfo part of allocator state (details)
  9. [DA][SDA] SyncDependenceAnalysis re-write (details)
  10. [VE] Support TargetBlockAddress (details)
  11. [ObjCARCAA][NewPM] Add already ported objc-arc-aa to PassRegistry.def (details)
  12. [mlir][openacc] Remove -allow-unregistred-dialect from ops and invalid tests (details)
  13. [llvm-exegesis] Add option to check the hardware support for a given feature before benchmarking. (details)
  14. scudo: Make it thread-safe to set some runtime configuration flags. (details)
  15. [test][SampleProfile][NewPM] Fix some tests under NPM (details)
  16. [asan][test] Several Posix/unpoison-alternate-stack.cpp fixes (details)
Changes
  1. [zorg] [PowerPC] Limit number of threads to 64 on clang-ppc64le-rhel buildbot (details)

Started by timer (13 times)

This run spent:

  • 2 hr 6 min waiting;
  • 2 hr 9 min build duration;
  • 4 hr 16 min total from scheduled to completion.
Revision: c2cc01b14ef84bee845318bde3ae623091934b96
  • refs/remotes/origin/master
Revision: 73fb9698c0573778787e77a8ffa57e7fa3caebd4
  • refs/remotes/origin/master
Revision: c2cc01b14ef84bee845318bde3ae623091934b96
  • refs/remotes/origin/master
Test Result (1 failure / ±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