Tooling: Track and verify CTS state #23
Open
Conversation
This file contains 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
fknorr
force-pushed
the
cts-state
branch
5 times, most recently
from
af56fed to
8132ae4
Compare
|
Now also renders a "CTS progress meter" in the readme. |
fknorr
force-pushed
the
cts-state
branch
2 times, most recently
from
83aaa7d to
5a0c42e
Compare
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.
Adds the "CTS State" Google Sheet I had lying around to the repo, and introduces a script to automatically build / run CTS tests to verify it's still up to date. This should make finding regressions and missed spec updates locally easier.
Eventually we want to integrate this into CI, but this requires KhronosGroup/SYCL-CTS/pull/871 to be merged first (+some CI integration work on our side).