[llvm-testresults] buildbot failure in lab.llvm.org on phase1 - sanity

[llvmlab-buildmaster at lab.llvm.org]

The Buildbot has detected a new failure on builder phase1 - sanity while building clang-tools-extra.
Full details are available at:
 http://lab.llvm.org:8013/builders/phase1%20-%20sanity/builds/10152

Buildbot URL: http://lab.llvm.org:8013/

Buildslave for this Build: macpro1

Build Reason: scheduler
Build Source Stamp: 188274
Blamelist: tasiraj

BUILD FAILED: failed

sincerely,
 -The Buildbot


================================================================================

CHANGES:
Files:
 cpp11-migrate/Core/FileOverrides.cpp
 cpp11-migrate/Core/FileOverrides.h
 cpp11-migrate/Core/Reformatting.cpp
 cpp11-migrate/Core/ReplacementsYaml.h
 cpp11-migrate/Core/Transform.cpp
 cpp11-migrate/tool/Cpp11Migrate.cpp
 test/cpp11-migrate/HeaderReplacements/common.cpp
 test/cpp11-migrate/HeaderReplacements/common.h
 test/cpp11-migrate/HeaderReplacements/common.h.yaml
 test/cpp11-migrate/HeaderReplacements/main.cpp
 unittests/cpp11-migrate/CMakeLists.txt
 unittests/cpp11-migrate/FileOverridesTest.cpp
 unittests/cpp11-migrate/IncludeExcludeTest.cpp
 unittests/cpp11-migrate/ReformattingTest.cpp
 unittests/cpp11-migrate/ReplacementsYamlTest.cpp
 unittests/cpp11-migrate/Utility.h
On: http://10.1.1.2/svn/llvm-project
For: clang-tools-extra
At: Tue 13 Aug 2013 08:06:28
Changed By: tasiraj
Comments: cpp11-migrate: Write header replacements to disk

Another attempt to commit r187204 after windows related problems has
been fixed. Note that changes to this patch reflect the current behavior
of cpp11-migrate.

Header replacements are now written to disk in YAML format for an external tool
to merge. A unique file will be created in the same directory as the header
with all replacements that came from a source file that included the header
file. The YAML file will have:
- Name of the header file
- Name of the source file that included the header file
- Transform ID that generated the replacement
- Offset
- Length
- Replacement text

Any tool reading these replacements should read them using the
HeaderChangeDocument struct.

Differential Revision: http://llvm-reviews.chandlerc.com/D1369

Properties: 




LOGS: