Started 5 days 17 hr ago
Took 1 hr 11 min on green-dragon-19

Failed Build rL:366017 - C:366013 - #57979 (Jul 14, 2019 5:42:44 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 366017
  • http://llvm.org/svn/llvm-project/cfe/trunk : 366013
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365982
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 365596
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365973
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365993
Changes
  1. [BitcodeReader] Use tighter upper bound to validate forward references.

    At the moment, bitcode files with invalid forward reference can easily
    cause the bitcode reader to run out of memory, by creating a forward
    reference with a very high index.

    We can use the size of the bitcode file as an upper bound, because a
    valid bitcode file can never contain more records. This should be
    sufficient to fail early in most cases. The only exception is large
    files with invalid forward references close to the file size.

    There are a couple of clusterfuzz runs that fail with out-of-memory
    because of very high forward references and they should be fixed by this
    patch.

    A concrete example for this is D64507, which causes out-of-memory on
    systems with low memory, like the hexagon upstream bots.

    Reviewers: t.p.northover, thegameg, jfb, efriedma, hfinkel

    Reviewed By: jfb

    Differential Revision: https://reviews.llvm.org/D64577 (detail/ViewSVN)
    by fhahn

Started by an SCM change

This run spent:

  • 6.3 sec waiting;
  • 1 hr 11 min build duration;
  • 1 hr 12 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.
Test Result (1 failure / -1)

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

Compile Error

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