Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch stabilization tests to new info #367

Merged
merged 2 commits into from
Mar 30, 2022
Merged

Switch stabilization tests to new info #367

merged 2 commits into from
Mar 30, 2022

Conversation

JLockerman
Copy link
Contributor

This commit switches the stabilization tests to the new stabilization info file, meaning there's exactly one central location that decides if things are stable. It also cleans the actual stabilization test code, and documents what invariants we're trying to maintain.

Copy link
Contributor

@rtwalker rtwalker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is also a use of INT here

CREATE AGGREGATE toolkit_experimental.lttb(ts TIMESTAMPTZ, value DOUBLE PRECISION, resolution INT) (\n\

There are multiple ways to refer to the integer type in SQL. The
canonical one is `integer`, and that's the one the scripts understand
the best, so update our remaining uses of `int` to `integer` for
consistency, and if hopes that if anyone copy/pastes a CREATE AGGREGATE
line for inspiration they'll use the correct name.
This commit switches the stabilization tests to the new stabilization
info file, meaning there's exactly one central location that decides if
things are stable. It also cleans the actual stabilization test code,
and documents what invariants we're trying to maintain.
@JLockerman
Copy link
Contributor Author

bors r+

@bors
Copy link
Contributor

bors bot commented Mar 30, 2022

Build succeeded:

@bors bors bot merged commit 665e9f6 into main Mar 30, 2022
@bors bors bot deleted the jl/stabalization-test branch March 30, 2022 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants