[runtimes] Officially deprecate the legacy testing configuration system
Add a warning and tweak the release note to explain that the deprecation
targets libc++, libc++abi and libuwnind as well.
Also, as a fly-by, ensure that our CI runs the legacy testing configuration
for libc++, libc++abi and libunwind. This doesn't matter too much since
it's deprecated, but we might as well test it properly.
Differential Revision: https://reviews.llvm.org/D126478
NOKEYCHECK=True
GitOrigin-RevId: 719bf2d9d9fdb8792b15d93364c9c6b2ddd68a36
diff --git a/docs/ReleaseNotes.rst b/docs/ReleaseNotes.rst
index 514de5d..b2bd071 100644
--- a/docs/ReleaseNotes.rst
+++ b/docs/ReleaseNotes.rst
@@ -148,7 +148,8 @@
its own headers.
- The legacy testing configuration is now deprecated and will be removed in the next release. For
- most users, this should not have any impact. However, if you are testing libc++ in a configuration
- or on a platform that used to be supported by the legacy testing configuration and isn't supported
- by one of the configurations in ``libcxx/test/configs``, please reach out to the libc++ developers
- to get your configuration supported officially.
+ most users, this should not have any impact. However, if you are testing libc++, libc++abi or
+ libunwind in a configuration or on a platform that used to be supported by the legacy testing
+ configuration and isn't supported by one of the configurations in ``libcxx/test/configs``,
+ ``libcxxabi/test/configs`` or ``libunwind/test/configs``, please move to one of those
+ configurations or define your own.