Started 2 yr 7 mo ago
Took 50 min on green-dragon-03

Failed Build r302008 (#5680) (May 3, 2017 3:45:05 AM)

Subproject Builds

Revision: 302008
Changes
  1. Check for lack of C++ context first when demangling

    Summary: It seems that if we have no context, then it can't possibly be a method.  Check that first.

    Reviewers: clayborg

    Reviewed By: clayborg

    Subscribers: labath, lldb-commits

    Differential Revision: https://reviews.llvm.org/D32708
    Patch by Scott Smith <scott.smith@purestorage.com>. (detail/ViewSVN)
    by labath
  2. [ELF] Fix problems with fabricateDefaultCommands() and --section-start

    The --section-start <name>=<address> needs to be translated into equivalent
    linker script commands. There are a couple of problems with the existing
    implementation:
    - The --section-start with the lowest address is assumed to be at the start
    of the map. This assumption is incorrect, we have to iterate through the
    SectionStartMap to find the lowest address.
    - The addresses in --section-start were being over-aligned when the
    sections were marked as PageAlign. This is inconsistent with the use of
    SectionStartMap in fixHeaders(), and can cause problems when the PageAlign
    causes an "unable to move location counter backward" error when the
    --section-start with PageAlign is aligned to an address higher than the next
    --section-start. The ld.bfd and ld.gold seem to be more consistent with this
    approach but this is not a well specified area.
       
    This change fixes the problems above and also corrects a typo in which
    fabricateDefaultCommands() is called with the wrong parameter, it should be
    called with AllocateHeader not Config->MaxPageSize.

    Differential Revision: https://reviews.llvm.org/D32749 (detail/ViewSVN)
    by psmith

Started by upstream project phase2_modules_relay build number 3850
originally caused by:

This run spent:

  • 8 ms waiting;
  • 50 min build duration;
  • 50 min total from scheduled to completion.

Identified problems

Subproject Failed

This job failed because one of the jobs triggered by it failed.
Indication 1