Started 1 mo 3 days ago
Took 4 hr 10 min on green-dragon-02

Failed Build #14720 (Sep 17, 2019 8:25:33 PM)

  • : 372197
  • : 372197
  • : 372143
  • : 371835
  • : 372034
  • : 372128
  1. [X86] Prevent assertion when calling a function that returns double with -mno-sse2 on x86-64.

    As seen in the most recent updates to PR10498 (detail)
    by ctopper
  2. [Remarks] Allow the RemarkStreamer to be used directly with a stream

    The filename in the RemarkStreamer should be optional to allow clients
    to stream remarks to memory or to existing streams.

    This introduces a new overload of `setupOptimizationRemarks`, and avoids
    enforcing the presence of a filename at different places. (detail)
    by thegameg
  3. [Timers] Fix printing some `-ftime-report` sections twice. Fixes PR40328.

    Starting from r324788 timer groups aren't cleared automatically when
    printed out. As a result some timer groups were printed one more time.
    For example, "Pass execution timing report" was printed again in
    `ManagedStatic<PassTimingInfo>` destructor, "DWARF Emission" in
    `ManagedStatic<Name2PairMap> NamedGroupedTimers` destructor.

    Fix by clearing timer groups manually.

    Reviewers: thegameg, george.karpenkov

    Reviewed By: thegameg

    Subscribers: aprantl, jkorous, dexonsmith, ributzka, aras-p, cfe-commits

    Differential Revision: (detail)
    by vsapsai
  4. [PGO] Change hardcoded thresholds for cold/inlinehint to use summary

    The PGO counter reading will add cold and inlinehint (hot) attributes
    to functions that are very cold or hot. This was using hardcoded
    thresholds, instead of the profile summary cutoffs which are used in
    other hot/cold detection and are more dynamic and adaptable. Switch
    to using the summary-based cold/hot detection.

    The hardcoded limits were causing some code that had a medium level of
    hotness (per the summary) to be incorrectly marked with a cold
    attribute, blocking inlining.

    Reviewers: davidxl

    Subscribers: llvm-commits

    Tags: #llvm

    Differential Revision: (detail)
    by tejohnson

Started by timer (4 times)

This run spent:

  • 3 hr 14 min waiting;
  • 4 hr 10 min build duration;
  • 7 hr 25 min 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

Regression test failed

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

Ninja target failed

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