99
1010// Welcome, Build Wrangler!
1111//
12- // A failure in this test indicates that there is a potential ABI breaking
13- // change in the Standard Library. If you observe a failure, please reach out to
14- // the Standard Library team directly to make sure we resolve this quickly!
12+ // This file lists APIs that are unique to stdlib builds with assertions.
13+ // (It is combined with the stability-stdlib-abi-without-asserts.test file
14+ // to generate a full list of potentially breaking API changes. In most cases
15+ // you'll want to edit that file instead of this one.)
1516//
16- // Please DO NOT XFAIL THIS TEST. In addition to ignoring the current set of ABI
17- // breaks, XFAILing this test also silences any future ABI breaks that may land
18- // on this branch, which isn't ideal.
17+ // A failure in this test indicates that there is a potential breaking change in
18+ // the Standard Library. If you observe a failure outside of a PR test, please
19+ // reach out to the Standard Library team directly to make sure this gets
20+ // resolved quickly! If your own PR fails in this test, you probably have an
21+ // ABI- or source-breaking change in your commits. Please go and fix it.
1922//
20- // Instead, consider extending the list of expected changes at the bottom. You
21- // can find a diff of what needs to be added in the output of the failed test
22- // run. The order of lines doesn't matter, and you can also include comments to
23- // refer to any bugs you filed .
23+ // Please DO NOT DISABLE THIS TEST. In addition to ignoring the current set of
24+ // ABI breaks, XFAILing this test also silences any future ABI breaks that may
25+ // land on this branch, which simply generates extra work for the next person
26+ // that picks up the mess .
2427//
25- // Thanks! -- Your friendly stdlib engineers
28+ // Instead of disabling this test, consider extending the list of expected
29+ // changes at the bottom. (You'll also need to do this if your own PR triggers
30+ // false positives, or if you have special permission to break things.) You can
31+ // find a diff of what needs to be added in the output of the failed test run.
32+ // The order of lines doesn't matter, and you can also include comments to refer
33+ // to any bugs you filed. Remember that in almost all cases you'll want to edit
34+ // the stability-stdlib-abi-without-asserts.test file instead of this one.
35+ //
36+ // Thank you for your help ensuring the stdlib remains compatible with its past!
37+ // -- Your friendly stdlib engineers
2638
2739// REQUIRES: swift_stdlib_asserts
2840
41+ // *** DO NOT DISABLE OR XFAIL THIS TEST. *** (See comment above.)
42+
2943// SR-13362
3044// We currently only have a baseline for Intel CPUs on macOS.
3145// REQUIRES: OS=macosx
3549// declarations are shuffled. rdar://problem/46618883
3650// UNSUPPORTED: swift_evolve
3751
38- // *** DO NOT XFAIL THIS TEST *** (See comment above.)
52+ // *** DO NOT DISABLE OR XFAIL THIS TEST. *** (See comment above.)
3953
4054Func _collectReferencesInsideObject(_:) is a new API without @available attribute
4155Func _loadDestroyTLSCounter() is a new API without @available attribute
@@ -44,3 +58,5 @@ Protocol _RuntimeFunctionCountersStats is a new API without @available attribute
4458Struct _GlobalRuntimeFunctionCountersState is a new API without @available attribute
4559Struct _ObjectRuntimeFunctionCountersState is a new API without @available attribute
4660Struct _RuntimeFunctionCounters is a new API without @available attribute
61+
62+ // *** DO NOT DISABLE OR XFAIL THIS TEST. *** (See comment above.)
0 commit comments