Skip to content

[Backport 7.7] Make assertions on job created in test #4671

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

Merged
merged 1 commit into from
Apr 23, 2020

Conversation

github-actions[bot]
Copy link
Contributor

Backport e5f523d from #4665

This commit updates the GetJobStatsApiTests to make
assertions on the job configured for the integration test.
This avoids grabbing a random job that may exist in the cluster
at the time the test concurrently runs.

The machine memory available to ML is also increased from
the default 30% to 50%, to avoid exceptions in running out
of memory, which have occurred locally on a machine with
32GB RAM when running all integration tests.
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

firstJob.ModelSizeStats.TotalByFieldCount.Should().Be(0);
firstJob.ModelSizeStats.TotalOverFieldCount.Should().Be(0);
firstJob.ModelSizeStats.TotalPartitionFieldCount.Should().Be(0);
var job = response.Jobs.Single(j => j.JobId == CallIsolatedValue);
Copy link
Member

Choose a reason for hiding this comment

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

👍

@Mpdreamz
Copy link
Member

Cluster Event processor timeout and security index failures which have been reported as issues already.

@Mpdreamz Mpdreamz merged commit ad9eaef into 7.7 Apr 23, 2020
@Mpdreamz Mpdreamz deleted the backport-4665-to-7.7 branch April 23, 2020 13:57
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.

3 participants