Closed reta closed 2 weeks ago
:x: Gradle check result for edb0cf8b5cb9d32ca0bd845d918e41402e5d0827: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
:x: Gradle check result for 330dc558a25f28db530a149a38bfff50b4344d92: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
:x: Gradle check result for cfc808835468e157dc2c28a5ab1eb3da100d8b62: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
@andrross mind taking a look please? thank you!
:x: Gradle check result for cfc808835468e157dc2c28a5ab1eb3da100d8b62: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
:x: Gradle check result for cfc808835468e157dc2c28a5ab1eb3da100d8b62: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?
:grey_exclamation: Gradle check result for cfc808835468e157dc2c28a5ab1eb3da100d8b62: UNSTABLE
1 org.opensearch.index.ShardIndexingPressureSettingsIT.testShardIndexingPressureEnforcedEnabledDisabledSetting
1 org.opensearch.index.ShardIndexingPressureSettingsIT.classMethod
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 71.54%. Comparing base (
b15cb0c
) to head (cfc8088
). Report is 263 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Thanks @reta! I'm wondering if we should backport this to earlier versions as well (I think this was first introduced in 2.11)?
Thanks @reta! I'm wondering if we should backport this to earlier versions as well (I think this was first introduced in 2.11)?
Thanks @jed326, I think we are not planing to release any patches for previous versions
Description
DATETIME_FORMATTER_CACHING_SETTING experimental feature should not default to 'true'
Related Issues
Closes https://github.com/opensearch-project/OpenSearch/issues/13411 (documentation update to follow shortly)
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check here.