Started 1 mo 10 days ago
Took 1 hr 53 min

Unstable Build clang-r362923-t57390-b57390.tar.gz (Jun 10, 2019 3:00:55 AM)

Issues

Found 1 issues:
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
AU        TEST.aa.report
AU        TEST.typesafe.Makefile
 U        .
At revision 362925

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
+ build get test-suite
+ . /Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-x86_64h-O3/config/tasks/utils/normalize_compiler.sh

Build Log

Revision: 362564
Changes
  1. [DebugInfo] More strict debug range for stack variables

    Variable's stack location can stretch longer than it should. If a
    variable is placed at the stack in a some nested basic block its range
    can be calculated to be up to the next occurrence of the variable's
    DBG_VALUE, or up to the end of the function, thus covering a basic
    blocks that should not be included in the variable’s location range.
    This happens because the DbgEntityHistoryCalculator ends register
    locations at the end of a basic block only if the variable’s location
    register has been changed throughout the function, which is not the
    case for the register used to reference stack objects.

    This patch also tries to produce a single value location if the location
    list builder managed to merge all the locations into one.

    Reviewers: aprantl, dstenb, jmorse

    Reviewed By: aprantl, dstenb, jmorse

    Subscribers: djtodoro, ivanbaev, asowda

    Tags: #debug-info

    Differential Revision: https://reviews.llvm.org/D61600 (detail)
    by nikolaprica

Started by upstream project relay-test-suite-verify-machineinstrs build number 5424
originally caused by:

This run spent:

  • 1 hr 31 min waiting;
  • 1 hr 53 min build duration;
  • 1 hr 53 min total from scheduled to completion.

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.