Conditionally test fallback/secondary queue via SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS

[sycl-issue-bot]

This issue was opened as a result of KhronosGroup/SYCL-Docs#615.

The CTS has an existing option SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS which enables / disables testing of deprecated features. Because KhronosGroup/SYCL-Docs#615 deprecates some features in SYCL-Next, we should conditionally test these features in SYCL-Next only when that option is enabled.

This opens a general question about how to handle SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS with a unified CTS. Some features (like the secondary queue) are deprecated only in SYCL-Next. Presumably, we want these features to be unconditionally tested when running the CTS in SYCL 2020 mode. However, when running the CTS in SYL-Next mode, they should be tested only when SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS is enabled.

Alternatively, we could decide that SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS is no longer needed, and we could remove that option from the CTS. Since deprecated features are still required by the specification, this option can't be used for conformance submissions anyway.

[gmlueck]

This PR only deprecates APIs, so those APIs are still supported. Any CTS tests we have for these APIs should remain.

[psalz]

Although we may want to wrap the corresponding tests in #if SYCL_CTS_ENABLE_DEPRECATED_FEATURES_TESTS. In general we'll have to decide whether we want to treat APIs that were deprecated in 2020 differently from those which are being deprecated in Next.

[gmlueck]

Why do we have an option to skip testing of deprecated APIs? Presumably, this option is not used for conformance since deprecated APIs are still part of the specification.

[psalz]

Why do we have an option to skip testing of deprecated APIs? Presumably, this option is not used for conformance since deprecated APIs are still part of the specification.

This option was introduced by Intel in #231

[gmlueck]

Why do we have an option to skip testing of deprecated APIs? Presumably, this option is not used for conformance since deprecated APIs are still part of the specification.

This option was introduced by Intel in #231

Thanks. I reopened this issue and changed the title to describe the problem.