Started 7 mo 10 days ago
Took 39 min

Failed Build clang-r360012-t56194-b56194.tar.gz (May 6, 2019 12:59:32 AM)

Issues

Found 1 issues:
Error: <html>
+ . /Users/buildslave/jenkins/workspace/lnt-test-suite-x86_64-Os-flto/config/tasks/utils/lnt_submit.sh
++ echo '@@@ LNT Submit @@@'
@@@ LNT Submit @@@
++ '[' -n http://104.154.54.203/db_default/v4/nts/submitRun -a -n lnt-test-suite-x86_64-Os-flto ']'
+++ lnt submit http://104.154.54.203/db_default/v4/nts/submitRun /Users/buildslave/jenkins/workspace/lnt-test-suite-x86_64-Os-flto/lnt-sandbox/report.json
++ LNT_RESULT_URL='error: <html>

<head><title>504 Gateway Time-out</title></head>
<body bgcolor="white">

Build Log

Revision: 358206
Changes
  1. [llvm-c] Make LLVMGetStringErrorTypeId a proper prototype

    In C a function declaration with an empty argument list isn't a real
    prototype, it will allow calling the function with any number of
    arguments. It will also cause warnings when used in C code compiled with
    '-Wstrict-prototypes'

    Reviewed By: whitequark
    Differential Revision: https://reviews.llvm.org/D61568 (detail)
    by andersg
Revision: 358206
Changes
  1. P1286R2: Remove restriction that the exception specification of a
    defaulted special member matches the implicit exception specification. (detail)
    by rsmith
  2. Use DiagRuntimeBehavior for -Wunsequenced to weed out false positives
    where either the modification or the other access is unreachable.

    This reverts r359984 (which reverted r359962). The bug in clang-tidy's
    test suite exposed by the original commit was fixed in r360009. (detail)
    by rsmith
Revision: 358206
Changes
  1. Fix test to avoid assuming clang will diagnose problems in unreachable code. (detail)
    by rsmith

Started by upstream project relay-lnt-test-suite build number 7214
originally caused by:

This run spent:

  • 8.7 sec waiting;
  • 39 min build duration;
  • 39 min total from scheduled to completion.

Identified problems

No identified problem

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