[SYCL][E2E] Add build-mode and run-mode to list of build-specific features
#17363
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aelovikov-intel
approved these changes
Mar 19, 2025
|
@ayylol , please merge |
|
@intel/llvm-gatekeepers this is ready to merge, thanks :) |
sarnex
pushed a commit
that referenced
this pull request
May 27, 2025
Currently when we check `REQUIRES`/`UNSUPPORTED` statements in `build-only` mode we throw an error if any feature that is not in `build_specific_features` evaluates to true. Since this is error will only trigger when a test queries for one of these features, it can be easy to miss adding new build-specific features to this list (see #17985, and #17363). This pr changes this check to be done for all features when in `build-only`, not just those queried by a test. If any available feature does not appear in `build_specific_features` then an error is thrown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We throw an error if a non build-specific feature is reported as true when in build-only (we expect this to never be the case), so when we do
UNSUPPORTED: build-onlythis would make the test unresolved.Also if we don't have
run-modemarked as a build specific feature when in build-only mode a test marked asREQUIRES: run-modewould run, since that feature would be considered "unknown" rather than false.