Started 25 days ago
Took 4 hr 26 min on green-dragon-02

Failed Build #14905 (Oct 18, 2019 1:26:27 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 375208
  • http://llvm.org/svn/llvm-project/cfe/trunk : 375199
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 375166
  • http://llvm.org/svn/llvm-project/zorg/trunk : 375205
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374854
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 375117
Changes
  1. [InstCombine] Fix miscompile bug in canEvaluateShuffled

    Summary:
    Add restrictions in canEvaluateShuffled to prevent that we for example
    transform

      %0 = insertelement <2 x i16> undef, i16 %a, i32 0
      %1 = srem <2 x i16> %0, <i16 2, i16 1>
      %2 = shufflevector <2 x i16> %1, <2 x i16> undef, <2 x i32> <i32 undef, i32 0>

    into

       %1 = insertelement <2 x i16> undef, i16 %a, i32 1
       %2 = srem <2 x i16> %1, <i16 undef, i16 2>

    as having an undef denominator makes the srem undefined (for all
    vector elements).

    Fixes: https://bugs.llvm.org/show_bug.cgi?id=43689

    Reviewers: spatel, lebedev.ri

    Reviewed By: spatel, lebedev.ri

    Subscribers: lebedev.ri, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D69038 (detail)
    by bjope
  2. [InstCombine] Pre-commit of test case showing miscompile bug in canEvaluateShuffled

    Adding the reproducer from  https://bugs.llvm.org/show_bug.cgi?id=43689,
    showing that instcombine is doing a bad transform. It transforms

      %0 = insertelement <2 x i16> undef, i16 %a, i32 0
      %1 = srem <2 x i16> %0, <i16 2, i16 1>
      %2 = shufflevector <2 x i16> %1, <2 x i16> undef, <2 x i32> <i32 undef, i32 0>

    into

       %1 = insertelement <2 x i16> undef, i16 %a, i32 1
       %2 = srem <2 x i16> %1, <i16 undef, i16 2>

    The undef denominator makes the whole srem undefined. (detail)
    by bjope
  3. Add LLVMGitPoller to listen for changes in the monorepo. (detail)
    by gkistanova
  4. Separate automatic schedulers for builders depending on is_legacy_mode.

    Changes from SVN should be scheduled for builders which checkout from SVN, changes from github should be scheduled for builders which checkout from github. For a transition period we need the both types of schedulers.

    Patch by Andrei Lebedev.

    Differential Revision: https://reviews.llvm.org/D69159 (detail)
    by gkistanova
  5. Refactored ClangBuilde.getClangCMakeBuildFactory and ClangBuilde.getClangCMakeGCSBuildFactory to support github.

    ClangBuilde.getClangBuildFactory, ClangBuilde.addClangGCCTests, ClangBuilde.addClangGDBTests, ClangBuilde.addModernClangGDBTests, and
    ClangBuilde.getClangTestsIgnoresFromPath are deprecated.

    Patch by Andrei Lebedev.

    Differential Revision: https://reviews.llvm.org/D69158 (detail)
    by gkistanova
  6. Added LLVMPoller to work with github.

    LLVM Git Poller functionally is the same as LLVM SVN Poller and will act as a drop in place replacement once the transition to github is complete.
    Based on the Buildbot 0.8.5 GitPoller.

    Patch by Alex Orlov.

    Differential Revision: https://reviews.llvm.org/D69154 (detail)
    by gkistanova
  7. [WebAssembly] -pthread implies -target-feature +sign-ext

    Summary:
    The sign extension proposal was motivated by a desire to not have
    separate sign-extending atomic operations, so it is meant to be
    enabled when threads are used.

    Reviewers: aheejin, dschuff

    Subscribers: sbc100, jgravelle-google, sunfish, jfb, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D69075 (detail)
    by tlively

Started by timer (5 times)

This run spent:

  • 4 hr 15 min waiting;
  • 4 hr 26 min build duration;
  • 8 hr 41 min total from scheduled to completion.

Identified problems

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
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

Regression test failed

This build failed because a regression test in the test suite FAILed. See the test report for details.
Indication 3

Ninja target failed

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

Missing test results

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