From 62997a373b4bcc50a88af32d31123ef741db683f Mon Sep 17 00:00:00 2001 From: Alastair Houghton Date: Tue, 6 Jun 2023 13:35:51 +0100 Subject: [PATCH] Disable Swift backtracer in a deliberately-crashing test. With the new backtracer enabled, you get extra output, so this test fails. rdar://110315737 --- Tests/Functional/TestCaseLifecycle/Misuse/main.swift | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Tests/Functional/TestCaseLifecycle/Misuse/main.swift b/Tests/Functional/TestCaseLifecycle/Misuse/main.swift index 6c01a5410..bf67eb871 100644 --- a/Tests/Functional/TestCaseLifecycle/Misuse/main.swift +++ b/Tests/Functional/TestCaseLifecycle/Misuse/main.swift @@ -1,5 +1,5 @@ // RUN: %{swiftc} %s -g -o %T/TestCaseLifecycleMisuse -// RUN: %T/TestCaseLifecycleMisuse > %t || true +// RUN: env SWIFT_BACKTRACE=enable=no %T/TestCaseLifecycleMisuse > %t || true // RUN: %{xctest_checker} %t %s #if os(macOS)