This repository was archived by the owner on May 9, 2024. It is now read-only.
Add an issue bucketing script for query execution tests #368
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 is a basic version that collects test statuses in presence of failures. It captures the return codes of standalone tests and creates a yaml report. The report is coarse-grained since each test may include many queries, but it gives some coverage picture. The intended use is to simplify status checking for non-standard build/run options (like
exec.heterogeneous.allow_cpu_retry = false
). For example, I've collected the stats forArrowBasedExecuteTest
on Intel GPU (we have 211 tests in total there, each includes multiple queries):Bucketing granularity can be easily improved by capturing the stderr. The help should be self-explanatory. Let me know if anything is unclear.