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

Avoid using TimeWarp in TransformIntegrationTests. #39277

Merged
merged 2 commits into from
Feb 22, 2019

Conversation

jtibshirani
Copy link
Contributor

@jtibshirani jtibshirani commented Feb 22, 2019

This commit makes TransformIntegrationTests into a standard integration test, as
opposed to using TimeWarp, which registers the mock component
ScheduleEngineTriggerMock to trigger watches.

The simplification may help with flakiness we've observed around TimeWarp, as in
#37882.

This commit makes TransformIntegrationTests into a standard integration test, as
opposed to using TimeWarp, which uses the mock component
ScheduleEngineTriggerMock to trigger watches.

The simplification may help with flakiness we've observed TimeWarp, as in
@jtibshirani jtibshirani added >test Issues or PRs that are addressing/adding tests :Data Management/Watcher v8.0.0 labels Feb 22, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@talevy talevy left a comment

Choose a reason for hiding this comment

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

direct calls to execution of the watch seem
alright to me! These tests were mocking this portion
of the integration anyways, and the test isn't interested
in testing scheduling. It is interested in transform script
execution.

Copy link
Contributor

@bizybot bizybot left a comment

Choose a reason for hiding this comment

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

LGTM, Thank you.

@jtibshirani
Copy link
Contributor Author

Thank you both for the review!

@jtibshirani jtibshirani merged commit a745b36 into elastic:master Feb 22, 2019
@jtibshirani jtibshirani deleted the watcher-transform-tests branch February 22, 2019 01:57
jtibshirani added a commit that referenced this pull request Feb 22, 2019
This commit makes `TransformIntegrationTests` into a standard integration test, as
opposed to using `TimeWarp`, which registers the mock component
`ScheduleEngineTriggerMock` to trigger watches.

The simplification may help with flakiness we've observed `TimeWarp, as in #37882.
jasontedor added a commit to DaveCTurner/elasticsearch that referenced this pull request Feb 22, 2019
* elastic/master:
  Ensure index commit released when testing timeouts (elastic#39273)
  Avoid using TimeWarp in TransformIntegrationTests. (elastic#39277)
  Fixed missed stopping of SchedulerEngine (elastic#39193)
  [CI] Mute CcrRetentionLeaseIT.testRetentionLeaseIsRenewedDuringRecovery (elastic#39269)
  Muting AutoFollowIT.testAutoFollowManyIndices (elastic#39264)
  Clarify the use of sleep in CCR test
  Fix testCannotShrinkLeaderIndex (elastic#38529)
  Fix CCR tests that manipulate transport requests
  Align generated release notes with doc standards (elastic#39234)
  Mute test (elastic#39248)
  ReadOnlyEngine should update translog recovery state information (elastic#39238)
  Wrap accounting breaker check in assertBusy (elastic#39211)
  Simplify and Fix Synchronization in InternalTestCluster (elastic#39168)
  [Tests] Make testEngineGCDeletesSetting deterministic (elastic#38942)
  Extend nextDoc to delegate to the wrapped doc-value iterator for date_nanos (elastic#39176)
  Change ShardFollowTask to reuse common serialization logic (elastic#39094)
  Replace superfluous usage of Counter with Supplier (elastic#39048)
  Disable bwc tests for elastic#39094
jtibshirani added a commit that referenced this pull request Feb 22, 2019
This commit makes `TransformIntegrationTests` into a standard integration test, as
opposed to using `TimeWarp`, which registers the mock component
`ScheduleEngineTriggerMock` to trigger watches.

The simplification may help with flakiness we've observed `TimeWarp, as in #37882.
jtibshirani added a commit that referenced this pull request Feb 22, 2019
This commit makes `TransformIntegrationTests` into a standard integration test, as
opposed to using `TimeWarp`, which registers the mock component
`ScheduleEngineTriggerMock` to trigger watches.

The simplification may help with flakiness we've observed `TimeWarp, as in #37882.
weizijun pushed a commit to weizijun/elasticsearch that referenced this pull request Feb 22, 2019
This commit makes `TransformIntegrationTests` into a standard integration test, as
opposed to using `TimeWarp`, which registers the mock component
`ScheduleEngineTriggerMock` to trigger watches.

The simplification may help with flakiness we've observed `TimeWarp, as in elastic#37882.
weizijun pushed a commit to weizijun/elasticsearch that referenced this pull request Feb 22, 2019
This commit makes `TransformIntegrationTests` into a standard integration test, as
opposed to using `TimeWarp`, which registers the mock component
`ScheduleEngineTriggerMock` to trigger watches.

The simplification may help with flakiness we've observed `TimeWarp, as in elastic#37882.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants