-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Rollup: Consolidate rollup cleanup for http tests #34342
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
Conversation
Pinging @elastic/es-search-aggs |
Note to self and others: we skip the rollup tests using gradle configuration in |
This issue tracks the rollup docs tests being disabled: #33319. |
@polyfractal, could you have a look at this when you get a chance? I think this is the last thing I need before I can fix the rollup docs tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for shuffling all this around @nik9000 :)
Thanks for reviewing @polyfractal! I've merged to master and am running the backport tests now. |
We'd disabled them because we didn't have a way to clean up after each test. I implemented elastic#34342 which adds the clean ups so now we can re-enable the tests. In the `setup` sections we have to use `raw` requests instead of `x-pack` requests because we don't have the json config for x-pack. Closes elastic#33319
This moves the rollup cleanup code for http tests from the high level rest client into the test framework and then entirely removes the rollup cleanup code for http tests that lived in x-pack. This is nice because it consolidates the cleanup into one spot, automatically invokes the cleanup without the test having to know that it is "about rollup", and should allow us to run the rollup docs tests. Part of #34530
All backported! |
We'd disabled them because we didn't have a way to clean up after each test. I implemented #34342 which adds the clean ups so now we can re-enable the tests. In the `setup` sections we have to use `raw` requests instead of `x-pack` requests because we don't have the json config for x-pack. Closes #33319
We'd disabled them because we didn't have a way to clean up after each test. I implemented #34342 which adds the clean ups so now we can re-enable the tests. In the `setup` sections we have to use `raw` requests instead of `x-pack` requests because we don't have the json config for x-pack. Closes #33319
This moves the rollup cleanup code for http tests from the high level rest client into the test framework and then entirely removes the rollup cleanup code for http tests that lived in x-pack. This is nice because it consolidates the cleanup into one spot, automatically invokes the cleanup without the test having to know that it is "about rollup", and should allow us to run the rollup docs tests. Part of #34530
We'd disabled them because we didn't have a way to clean up after each test. I implemented #34342 which adds the clean ups so now we can re-enable the tests. In the `setup` sections we have to use `raw` requests instead of `x-pack` requests because we don't have the json config for x-pack. Closes #33319
This moves the rollup cleanup code for http tests from the high level rest
client into the test framework and then entirely removes the rollup cleanup
code for http tests that lived in x-pack. This is nice because it
consolidates the cleanup into one spot, automatically invokes the cleanup
without the test having to know that it is "about rollup", and should allow
us to run the rollup docs tests.
Part of #34530