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

DatafeedJobsIT#testDatafeedTimingStats_DatafeedRecreated fails #63973

Open
javanna opened this issue Oct 21, 2020 · 5 comments
Open

DatafeedJobsIT#testDatafeedTimingStats_DatafeedRecreated fails #63973

javanna opened this issue Oct 21, 2020 · 5 comments
Labels
medium-risk An open issue or test failure that is a medium risk to future releases :ml Machine learning Team:ML Meta label for the ML team >test-failure Triaged test failures from CI

Comments

@javanna
Copy link
Member

javanna commented Oct 21, 2020

Build scan: https://gradle-enterprise.elastic.co/s/weggtbiofm7zw/console-log?task=:x-pack:plugin:ml:qa:native-multi-node-tests:integTestRunner

Repro line: ./gradlew ':x-pack:plugin:ml:qa:native-multi-node-tests:integTestRunner' --tests "org.elasticsearch.xpack.ml.integration.DatafeedJobsIT.testDatafeedTimingStats_DatafeedRecreated" -Dtests.seed=862B982F15848C7 -Dtests.security.manager=true -Dtests.locale=ro-RO -Dtests.timezone=Africa/Mogadishu -Druntime.java=8 -Dtests.fips.enabled=true

Reproduces locally?: no

Applicable branches: any

Failure history:
This test has been failing every once in a while in the last months, hard to say when it started. Not sure why an issue was not logged, there seems to be #44335 but it's a very old one.

Failure excerpt:

 
  | org.elasticsearch.xpack.ml.integration.DatafeedJobsIT > testDatafeedTimingStats_DatafeedRecreated FAILED |  
  | java.lang.AssertionError: |  
  | Expected: a value greater than <0L> |  
  | but: <0L> was equal to <0L> |  
  | at __randomizedtesting.SeedInfo.seed([862B982F15848C7:CF35BA87409F0E03]:0) |  
  | at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18) |  
  | at org.junit.Assert.assertThat(Assert.java:956) |  
  | at org.junit.Assert.assertThat(Assert.java:923) |  
  | at org.elasticsearch.xpack.ml.integration.DatafeedJobsIT.assertDatafeedStats(DatafeedJobsIT.java:272) |  
  | at org.elasticsearch.xpack.ml.integration.DatafeedJobsIT.lambda$testDatafeedTimingStats_DatafeedRecreated$5(DatafeedJobsIT.java:178) |  
  | at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:951) |  
  | at org.elasticsearch.xpack.ml.integration.DatafeedJobsIT.lambda$testDatafeedTimingStats_DatafeedRecreated$6(DatafeedJobsIT.java:175) |  
  | at org.elasticsearch.xpack.ml.integration.DatafeedJobsIT.testDatafeedTimingStats_DatafeedRecreated(DatafeedJobsIT.java:185)

@javanna javanna added >test-failure Triaged test failures from CI :ml Machine learning labels Oct 21, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@droberts195
Copy link
Contributor

@przemekwitek please could you take a look at this one?

I see at the end of the test it calls openAndRunJob twice:

The comment // Datafeed processed numDocs documents so search_count must be greater than 0. in that lambda is only true for the first run of the datafeed. The datafeed gets deleted and recreated but the data counts are from the job which doesn't get deleted and recreated. So second time through it's expected that the datafeed finds no documents. I can see that it ought to do a search to determine that there are no extra documents, but maybe there's uncertainty about how quickly it will do this if it already appears to be up-to-date (if the results of the first invocation are within the last query_delay seconds)?

@przemekwitek
Copy link
Contributor

I'm taking a look at this issue now...

@droberts195
Copy link
Contributor

Assigning medium-risk due to loss of test coverage from muting.

@droberts195 droberts195 added the medium-risk An open issue or test failure that is a medium risk to future releases label Oct 10, 2023
@elasticsearchmachine elasticsearchmachine added the Team:ML Meta label for the ML team label Oct 10, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

@przemekwitek przemekwitek removed their assignment Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium-risk An open issue or test failure that is a medium risk to future releases :ml Machine learning Team:ML Meta label for the ML team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

5 participants