Vector Verification: Rework to run based on env variable DUCKDB_DEBUG_VERIFY_VECTOR
and move to Main.yml
#16957
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.
This PR modifies the vector verification tests so they run based on an environment variable, e.g.:
This then allows all of the vector verification tests to be run in a single workflow instead of requiring multiple re-compilations.
We move this workflow from nightly to
Main.yml
as well.In addition, we fix a minor bug with
Reinterpret
on dictionary vectors which fixes an issue in the sequence operator verification run.