File: TestStdModuleBuildErrors.py

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-12
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,496,180 kB
  • sloc: cpp: 5,593,972; ansic: 986,872; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,538; xml: 953; cs: 573; fortran: 567
file content (61 lines) | stat: -rw-r--r-- 2,587 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
"""
Tests that the import-std-module=fallback setting is only showing the error
diagnostics from the first parse attempt which isn't using a module.
This is supposed to prevent that a broken libc++ module renders failing
expressions useless as the original failing errors are suppressed by the
module build errors.
"""

from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
import os


class TestCase(TestBase):

    mydir = TestBase.compute_mydir(__file__)

    # We only emulate a fake libc++ in this test and don't use the real libc++,
    # but we still add the libc++ category so that this test is only run in
    # test configurations where libc++ is actually supposed to be tested.
    @add_test_categories(["libc++"])
    @skipIfRemote
    @skipIf(compiler=no_match("clang"))
    def test(self):
        self.build()

        sysroot = os.path.join(os.getcwd(), "root")

        # Set the sysroot this test is using to provide a custom libc++.
        self.runCmd("platform select --sysroot '" + sysroot + "' host",
                    CURRENT_EXECUTABLE_SET)

        lldbutil.run_to_source_breakpoint(self,
                                          "// Set break point at this line.",
                                          lldb.SBFileSpec("main.cpp"))

        # The expected error message when the fake libc++ module in this test
        # fails to build from within LLDB (as it contains invalid code).
        module_build_error_msg = "unknown type name 'random_token_to_fail_the_build'"

        # First force the std module to be imported. This should show the
        # module build error to the user.
        self.runCmd("settings set target.import-std-module true")
        self.expect("expr (size_t)v.size()",
                    substrs=[module_build_error_msg],
                    error=True)

        # In the fallback mode the module build error should not be shown.
        self.runCmd("settings set target.import-std-module fallback")
        fallback_expr = "expr v ; error_to_trigger_fallback_mode"
        # First check for the actual expression error that should be displayed
        # and is useful for the user.
        self.expect(fallback_expr,
                    substrs=["use of undeclared identifier 'error_to_trigger_fallback_mode'"],
                    error=True)
        # Test that the module build error is not displayed.
        self.expect(fallback_expr,
                    substrs=[module_build_error_msg],
                    matching=False,
                    error=True)