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

Bumping Node Indices Stats Optimisation to 2.17 #15514

Conversation

Pranshu-S
Copy link
Contributor

Description

Bumping node indices stats optimisation to 2.17. #14454

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

#13340

Check List

  • Functionality includes testing.
    - [ ] API changes companion pull request created, if applicable.
    - [ ] Public documentation issue/PR created, if applicable.

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.]

Copy link
Contributor

❌ Gradle check result for c7b0e25: 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?

@dblock
Copy link
Member

dblock commented Sep 2, 2024

Won't hold this for a CHANGELOG, but I think something like "Improved performance of X ..." would be a good idea.

Copy link
Contributor

github-actions bot commented Sep 2, 2024

❌ Gradle check result for c7b0e25: 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?

Signed-off-by: Pranshu Shukla <[email protected]>
Copy link
Contributor

github-actions bot commented Sep 3, 2024

❌ Gradle check result for 4780a8f: 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?

Copy link
Contributor

github-actions bot commented Sep 4, 2024

❌ Gradle check result for 4780a8f: null

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?

1 similar comment
Copy link
Contributor

github-actions bot commented Sep 4, 2024

❌ Gradle check result for 4780a8f: null

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?

Copy link
Contributor

github-actions bot commented Sep 4, 2024

❌ Gradle check result for 4780a8f: 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?

@Pranshu-S Pranshu-S force-pushed the NodeIndicesStatsOptimisationBumpVersion branch from 93143d3 to 75e1232 Compare September 5, 2024 03:37
Signed-off-by: Pranshu Shukla <[email protected]>
@shwetathareja
Copy link
Member

@Pranshu-S please rebase from main

Copy link
Contributor

github-actions bot commented Sep 5, 2024

❌ Gradle check result for 93143d3: 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?

@Pranshu-S
Copy link
Contributor Author

@Pranshu-S please rebase from main

Merged from main.

Copy link
Contributor

github-actions bot commented Sep 5, 2024

❌ Gradle check result for 75e1232: 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?

Copy link
Contributor

github-actions bot commented Sep 5, 2024

❌ Gradle check result for 4344ff9: 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?

Copy link
Contributor

github-actions bot commented Sep 5, 2024

❌ Gradle check result for 4780a8f: 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?

@Pranshu-S
Copy link
Contributor Author

Closing in virtue of - #15709

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.

3 participants