llvm-project/lldb/packages/Python/lldbsuite/test_event/build_exception.py

class BuildError(Exception):

    def __init__(self, called_process_error):
        super(BuildError, self).__init__("Error when building test subject")
        self.command = called_process_error.lldb_extensions.get(
            "command", "<command unavailable>")
        self.build_error = called_process_error.lldb_extensions["combined_output"]

    def __str__(self):
        return self.format_build_error(self.command, self.build_error)

    @staticmethod
    def format_build_error(command, command_output):
        return "Error when building test subject.\n\nBuild Command:\n{}\n\nBuild Command Output:\n{}".format(
            command, command_output.decode("utf-8"))
surface build error content through test event system Summary: print build errors nicely in test output This test infrastructure change adds a new Python exception for test subject builds that fail. The output of the build command is captured and propagated to both the textual test output display code and to the test event system. The ResultsFormatter objects have been modified to do something more useful with this information. The xUnit formatter now replaces the non-informative Python build error stacktrace with the build error content. The curses ResultsFormatter prints a 'B' for build errors rather than 'E'. The xUnit output, in particular, makes it much easier for developers to track down test subject build errors that cause test failures when reports come in from CI. Reviewers: granata.enrico Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D20252 llvm-svn: 269525 2016-05-14 00:42:30 +00:00			`class BuildError(Exception):`
* This commit represents a complete reformatting of the LLDB source code * to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname ".c" -or -iname ".cpp" -or -iname ".h" -or -iname ".mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751 2016-09-06 20:57:50 +00:00
surface build error content through test event system Summary: print build errors nicely in test output This test infrastructure change adds a new Python exception for test subject builds that fail. The output of the build command is captured and propagated to both the textual test output display code and to the test event system. The ResultsFormatter objects have been modified to do something more useful with this information. The xUnit formatter now replaces the non-informative Python build error stacktrace with the build error content. The curses ResultsFormatter prints a 'B' for build errors rather than 'E'. The xUnit output, in particular, makes it much easier for developers to track down test subject build errors that cause test failures when reports come in from CI. Reviewers: granata.enrico Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D20252 llvm-svn: 269525 2016-05-14 00:42:30 +00:00			`def __init__(self, called_process_error):`
			`super(BuildError, self).__init__("Error when building test subject")`
			`self.command = called_process_error.lldb_extensions.get(`
			`"command", "<command unavailable>")`
[lldb] add printing of stdout compile errors to lldbsuite Summary: Add printing of the output of stdout during compile errors, in addition to stderr output. Reviewed By: labath Differential Revision: https://reviews.llvm.org/D83425 2020-07-22 16:22:59 +02:00			`self.build_error = called_process_error.lldb_extensions["combined_output"]`
surface build error content through test event system Summary: print build errors nicely in test output This test infrastructure change adds a new Python exception for test subject builds that fail. The output of the build command is captured and propagated to both the textual test output display code and to the test event system. The ResultsFormatter objects have been modified to do something more useful with this information. The xUnit formatter now replaces the non-informative Python build error stacktrace with the build error content. The curses ResultsFormatter prints a 'B' for build errors rather than 'E'. The xUnit output, in particular, makes it much easier for developers to track down test subject build errors that cause test failures when reports come in from CI. Reviewers: granata.enrico Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D20252 llvm-svn: 269525 2016-05-14 00:42:30 +00:00
			`def __str__(self):`
			`return self.format_build_error(self.command, self.build_error)`

			`@staticmethod`
			`def format_build_error(command, command_output):`
			`return "Error when building test subject.\n\nBuild Command:\n{}\n\nBuild Command Output:\n{}".format(`
[build_exception] Decode build failure messages This is so that the test harness pretty-prints build error messages in trace mode, instead of dumping a raw python bytes object. llvm-svn: 369987 2019-08-26 23:24:45 +00:00			`command, command_output.decode("utf-8"))`