Skip to content

[7.x] [ML] Functional tests - fix job validation API test with maxModelMemoryLimit (#68501) #68628

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.

Sign up for GitHub

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

Merged
pheyos merged 1 commit into from
Jun 9, 2020
Merged

[7.x] [ML] Functional tests - fix job validation API test with maxModelMemoryLimit (#68501) #68628

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions x-pack/test/api_integration/apis/ml/job_validation/validate.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,15 @@ export default ({ getService }: FtrProviderContext) => {
.send(requestBody)
.expect(200);

// The existance and value of maxModelMemoryLimit depends on ES settings
// and may vary between test environments, e.g. cloud vs non-cloud,
// so it should not be part of the validation
body.forEach((element: any) => {
if (element.hasOwnProperty('maxModelMemoryLimit')) {
delete element.maxModelMemoryLimit;
}
});

expect(body).to.eql([
{
id: 'job_id_valid',
Expand Down