Started 11 mo ago
Took 1 hr 13 min

Unstable Build clang-d343328-g5125803d344-t7044-b7044.tar.gz (Feb 21, 2020 8:51:12 AM)


Found 1 issues:
Error: call to constructor of 'llvm::APInt' is ambiguous"
Fetching upstream changes from http://labmaster3.local/git/llvm-project.git
 > git fetch --tags --progress -- http://labmaster3.local/git/llvm-project.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse 5125803d344^{commit} # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5125803d344b848cdfc9441edfcc36dc8e488407 # timeout=10
Commit message: "[mlir] Silence error: call to constructor of 'llvm::APInt' is ambiguous"
 > git rev-list --no-walk c51b0bede82b9eeddce78151dfc257cf738bf367 # timeout=10
[Pipeline] }

Build Log

  1. [mlir] Add a signedness semantics bit to IntegerType (details)
  2. [TargetLowering] SimplifyDemandedBits - use getValidShiftAmountConstant helper. (details)
  3. [X86] Regenerate hi reg tests (details)
  4. [Error/unittests] Add a FailedWithMessage gtest matcher (details)
  5. [PowerPC][NFC] Remove Darwin specific logic in frame finalization. (details)
  6. [AST][NFC] Update outdated comments in ASTStructuralEquivalence.cpp (details)
  7. [PowerPC][NFC] Add a test for vrsave usage iinline asm. (details)
  8. [lldb/DWARF] Add support for type units in dwp files (details)
  9. Remove unused functions in llvm-ml (details)
  10. [mlir] Silence error: call to constructor of 'llvm::APInt' is ambiguous (details)

Started by upstream project relay-test-suite-verify-machineinstrs build number 7134
originally caused by:

This run spent:

  • 7.3 sec waiting;
  • 1 hr 13 min build duration;
  • 1 hr 13 min total from scheduled to completion.
Revision: 3a4296e9c1cdb53e0bf939b244790d257a6d5f26
  • refs/remotes/origin/master
Revision: 5125803d344b848cdfc9441edfcc36dc8e488407
  • detached
Revision: e630ecf2f321b7a37e915a51088983bb109f0d6a
  • refs/remotes/origin/master
Revision: 0d59095493ec8d189240307396e28105fc75ac37
  • refs/remotes/origin/master

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.