-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Migrate x-pack-enrich legacy rest tests to new test framework #131743
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
Migrate x-pack-enrich legacy rest tests to new test framework #131743
Conversation
Pinging @elastic/es-core-infra (Team:Core/Infra) |
YAML tests are failing in cleanUpCluster. Not sure how to solve, if preserving the data I get conflicts later.
|
x-pack/plugin/enrich/build.gradle
Outdated
|
||
clusterModules project(xpackModule('monitoring')) | ||
clusterModules project(xpackModule('ilm')) | ||
clusterModules project(xpackModule('wildcard')) | ||
} | ||
|
||
addQaCheckDependencies(project) |
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.
We can remove this since we've gotten rid of the QA projects.
Hmm, I don't see why it would be different. The only change we've really made here behaviorally is switching away from the default distribution which certainly could matter. Might be worth trying to see if using the default distro resolves the failures. Perhaps there's another missing module here we implicitly rely on? |
Thanks @mark-vieira, using the default distro the YAML tests pass. No idea why 🤷 |
💔 Backport failed
You can use sqren/backport to manually backport by running |
…c#131743) (cherry picked from commit 71130a6) # Conflicts: # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/RestrictedBuildApiService.java # x-pack/plugin/enrich/build.gradle # x-pack/plugin/enrich/qa/rest-with-advanced-security/build.gradle # x-pack/plugin/enrich/qa/rest-with-security/build.gradle # x-pack/plugin/enrich/qa/rest/build.gradle
@mark-vieira actually, noticed one thing... how's FIPS working in the new test framework, that requires additional jars doesn't it? |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…king * upstream/main: (90 commits) Register a blob cache long counter metric for total evicted regions (elastic#131862) Move plan attribute resolution to its own component (elastic#131830) Make restore support multi-project (elastic#131661) Use logically more correct expression (elastic#131869) [ES|QL] Change equals and hashcode for ConstantNullBlock (elastic#131817) Update `TransportVersion` to support a new model (elastic#131488) Correct slow log user for RCS 2.0 (elastic#130140) Revert "Remove 8.17 from dev branches" Mute org.elasticsearch.compute.aggregation.ValuesBytesRefGroupingAggregatorFunctionTests testSomeFiltered elastic#131878 Remove 8.17 from dev branches Revert "CompressorFactory.compressor (elastic#131655)" (elastic#131866) Add fast path for single value in VALUES aggregator (elastic#130510) Resolve inference release tests failing due to missing feature flag (elastic#131841) [Docs] Replace placeholder URLs (elastic#131309) CompressorFactory.compressor (elastic#131655) add availability info for speed loading setting (elastic#131714) [Logstash] Move `elastic_integration` plugin usage to ES logstash-bridge. (elastic#131486) Migrate x-pack-enrich legacy rest tests to new test framework (elastic#131743) Fix plugin example test failures due to deprecation warning (elastic#131819) Remove deprecated function isNotNullAndFoldable (elastic#130944) ...
It works more or less the same way. See |
Migrate x-pack-enrich legacy rest tests to new test framework