Skip to content

Fix spurious test failure during back deployment tests #28071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 5, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions test/Interpreter/bridged_casts_folding.swift
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@
// the correct reason in the test. We want to separate a memory management error
// from a cast error which prints a nice error message.

// FIXME: we should run this test if the OS-provided stdlib is recent enough.
// UNSUPPORTED: use_os_stdlib

// REQUIRES: executable_test
// REQUIRES: objc_interop

Expand Down
1 change: 1 addition & 0 deletions test/lit.cfg
Original file line number Diff line number Diff line change
Expand Up @@ -1461,6 +1461,7 @@ if not kIsWindows:
"SIMCTL_CHILD_DYLD_LIBRARY_PATH='{0}' " # Simulator option
.format(target_stdlib_path, libdispatch_path)) + config.target_run
else:
config.available_features.add('use_os_stdlib')
os_stdlib_path = ''
if run_vendor == 'apple':
#If we get swift-in-the-OS for non-Apple platforms, add a condition here
Expand Down