Skip to content

[CI] data_frame/transforms_start_stop/Test start/stop/start transform failed #47441

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

Closed
droberts195 opened this issue Oct 2, 2019 · 2 comments · Fixed by #47867
Closed

[CI] data_frame/transforms_start_stop/Test start/stop/start transform failed #47441

droberts195 opened this issue Oct 2, 2019 · 2 comments · Fixed by #47867
Assignees
Labels
:ml/Transform Transform >test-failure Triaged test failures from CI

Comments

@droberts195
Copy link
Contributor

org.elasticsearch.xpack.test.rest.XPackRestIT test {p0=transform/transforms_start_stop/Test start/stop only starts/stops specified transform} failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=openjdk12,ES_RUNTIME_JAVA=zulu11,nodes=general-purpose/240/console (scan https://gradle-enterprise.elastic.co/s/5ue2zwsinn5fi)

The error was:

  2> java.lang.AssertionError: Failure at [transform/transforms_start_stop:276]: field [transforms.0.state] was expected to match the provided regex but didn't
    Expected: started|indexing
         but: was "stopped"

        Caused by:
        java.lang.AssertionError: field [transforms.0.state] was expected to match the provided regex but didn't
        Expected: started|indexing
             but: was "stopped"

This doesn't reproduce consistently with:

./gradlew ':x-pack:plugin:integTestRunner' --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=transform/transforms_start_stop/Test start/stop only starts/stops specified transform}" \
  -Dtests.seed=89EE627200B8B896 \
  -Dtests.security.manager=true \
  -Dtests.locale=gu-IN \
  -Dtests.timezone=Africa/Accra \
  -Dcompiler.java=12 \
  -Druntime.java=11 \
  -Dtests.rest.blacklist=getting_started/10_monitor_cluster_health/*
@droberts195 droberts195 added >test-failure Triaged test failures from CI :ml/Transform Transform labels Oct 2, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transforms)

@droberts195
Copy link
Contributor Author

@hendrikmuhs hendrikmuhs self-assigned this Oct 10, 2019
hendrikmuhs pushed a commit that referenced this issue Oct 11, 2019
Batch transforms automatically stop after all data has processed, therefore tests can not reliable test the state. This change rewrites tests to remove the unreliable tests or use continuous transforms instead as they do not auto-stop.

fixes #47441
hendrikmuhs pushed a commit that referenced this issue Oct 11, 2019
Batch transforms automatically stop after all data has processed, therefore tests can not reliable test the state. This change rewrites tests to remove the unreliable tests or use continuous transforms instead as they do not auto-stop.

fixes #47441
howardhuanghua pushed a commit to TencentCloudES/elasticsearch that referenced this issue Oct 14, 2019
)

Batch transforms automatically stop after all data has processed, therefore tests can not reliable test the state. This change rewrites tests to remove the unreliable tests or use continuous transforms instead as they do not auto-stop.

fixes elastic#47441
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:ml/Transform Transform >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants