Started 2 yr 5 mo ago
Took 9 hr 4 min on green-dragon-22

Failed Build #73 (Nov 28, 2018 11:19:52 PM)

Revisions
  • http://llvm.org/svn/llvm-project/clang-tools-extra/branches/release_70 : 341829
  • http://llvm.org/svn/llvm-project/llvm/branches/release_70 : 347811
  • http://llvm.org/svn/llvm-project/cfe/branches/release_70 : 347834
  • http://llvm.org/svn/llvm-project/debuginfo-tests/branches/release_70 : 338681
  • http://llvm.org/svn/llvm-project/libcxx/branches/release_70 : 341529
  • http://llvm.org/svn/llvm-project/compiler-rt/branches/release_70 : 341524
Changes
  1. Merging r345497:

    ------------------------------------------------------------------------
    r345497 | asavonic | 2018-10-29 04:14:01 -0700 (Mon, 29 Oct 2018) | 29 lines

    [OpenCL] Fix serialization of OpenCLExtensionDecls

    Summary:
    I recently discovered that adding the following code into `opencl-c.h` causes
    failure of `test/Headers/opencl-c-header.cl`:
    ```
    #pragma OPENCL EXTENSION cl_my_ext : begin
    void cl_my_ext_foobarbaz();
    #pragma OPENCL EXTENSIOn cl_my_ext : end
    ```

    Clang crashes at the assertion is `ASTReader::getGlobalSubmoduleID()`:
    ```
    assert(I != M.SubmoduleRemap.end() && "Invalid index into submodule index remap");
    ```

    The root cause of the problem that to deserialize `OPENCL_EXTENSION_DECLS`
    section `ASTReader` needs to deserialize a Decl contained in it. In turn,
    deserializing a Decl requires information about whether this declaration is
    part of a (sub)module, but this information is not read yet because it is
    located further in a module file.

    Reviewers: Anastasia, yaxunl, JDevlieghere

    Reviewed By: Anastasia

    Subscribers: sidorovd, cfe-commits, asavonic

    Differential Revision: https://reviews.llvm.org/D53200
    ------------------------------------------------------------------------ (detail/ViewSVN)
    by tstellar
  2. Merging r343105:

    ------------------------------------------------------------------------
    r343105 | lebedevri | 2018-09-26 06:08:44 -0700 (Wed, 26 Sep 2018) | 17 lines

    [analyzer] scan-build: if --status-bugs is passed, don't forget about the exit status of the actual build

    Summary:
    This has been bothering me for a while, but only now i have actually looked into this.
    I'm using one CI job for static analysis - clang static analyzers as compilers + clang-tidy via cmake.
    And i'd like for the build to fail if at least one of those finds issues.
    If clang-tidy finds issues, it will fail the build since the warnings-as-errors is set.
    If static analyzer finds anything, since --status-bugs is set, it will fail the build.
    But if clang-tidy find anything, but static analyzer does not, the build succeeds :/

    Reviewers: sylvestre.ledru, alexfh, jroelofs, ygribov, george.karpenkov, krememek

    Reviewed By: jroelofs

    Subscribers: xazax.hun, szepet, a.sidorin, mikhail.ramalho, Szelethus, cfe-commits

    Differential Revision: https://reviews.llvm.org/D52530
    ------------------------------------------------------------------------ (detail/ViewSVN)
    by tstellar

Started by upstream project clang-stage1-cmake-RA-expensive_release_70 build number 106
originally caused by:

This run spent:

  • 4 hr 56 min waiting;
  • 9 hr 4 min build duration;
  • 14 hr total from scheduled to completion.

Identified problems

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 1

Compile Error

This build failed because of a compile error. Below is a list of all errors in the build log:
Indication 2

Ninja target failed

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