-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
[SR-1124] Drop FileCheck from test/1_stdlib, use StdlibUnittest instead #43737
Comments
I'm a little concerned that we'll lose what little coverage we have for the interpreter; right now there's a (non-buildbot) test mode that turns simple compile-and-run invocations into interpreter invocations. StdlibUnittest currently doesn't support that because it runs all tests out of process by default. I should probably file a bug for this. |
Comment by Kyle Yoon (JIRA) Is this task mostly changing // RUN: %target-run %t/ArrayBridge > %t.txt into // RUN: %target-run-stdlib-swift | FileCheck %s for the listed files? Sorry for all the questions, again! |
No need to apologize for clarifying the task! On the contrary, thanks for these follow-up questions. The ideal end state of the listed tests would be the following: // RUN: %target-run-simple-swift A good example is |
Comment by Sammy Gutierrez (JIRA) Here is the work I have for this ticket. I was hoping someone could take a quick look over it before submitting the PR (should I ask for help in the forums instead?). I attempted to remove FileCheck from any files that I could in
|
Resetting assignee for all Starter Bugs not modified since 2018. I think we lost this one since it wasn't a full PR. In the future, please feel free to make a PR even if it's still WIP. |
Additional Detail from JIRA
md5: 5245d992633498d3acacd3655548dd7c
Issue Description:
Swift's test/1_stdlib directory is meant to include tests for the Swift stdlib. Most of these are written using the testing framework designed for this purpose, StdlibUnittest. However, some use an ad-hoc system of printing strings to stdout, then checking the output via FileCheck.
The following tests should be written using StdlibUnittest (and no longer reference FileCheck):
test/1_stdlib/ArrayBridge.swift
test/1_stdlib/BitwiseOperationsType.swift
test/1_stdlib/BridgeNonVerbatim.swift
test/1_stdlib/Bridgeable.swift
test/1_stdlib/CGGeometry.swift
test/1_stdlib/Collection.swift
test/1_stdlib/CollectionOfOne.swift
test/1_stdlib/Float.swift
test/1_stdlib/FloatingPointIR.swift
test/1_stdlib/HeapBuffer.swift
test/1_stdlib/ImplicitlyUnwrappedOptional.swift
test/1_stdlib/KVO.swift
test/1_stdlib/LogicValue.swift
test/1_stdlib/Map.swift
test/1_stdlib/NSObject.swift
test/1_stdlib/NSUndoManager.swift
test/1_stdlib/NewArray.swift.gyb
test/1_stdlib/NewString.swift
test/1_stdlib/NewStringAppending.swift
test/1_stdlib/Nil.swift
test/1_stdlib/Reflection.swift
test/1_stdlib/Reflection_jit.swift
test/1_stdlib/Reflection_objc.swift
test/1_stdlib/SegmentAlignment.c
test/1_stdlib/SpriteKit.swift
test/1_stdlib/StringReallocation.swift
test/1_stdlib/TypeName.swift
test/1_stdlib/UIKit.swift
test/1_stdlib/UIViewControllerAdditions.swift
test/1_stdlib/VarArgs.swift
test/1_stdlib/Zip.swift
test/1_stdlib/alloc_rounding.swift
test/1_stdlib/integer_conversions.swift
test/1_stdlib/sort_integers.swift
test/1_stdlib/subString.swift
The text was updated successfully, but these errors were encountered: