-
Notifications
You must be signed in to change notification settings - Fork 119
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
Add further creation waits to notebooks tests #1270
Conversation
Signed-off-by: Simeon Widdis <sawiddis@amazon.com>
Signed-off-by: Simeon Widdis <sawiddis@amazon.com>
Signed-off-by: Simeon Widdis <sawiddis@amazon.com>
After discussing with the team, we decided to keep the refresh/reload logic present while still checking for creation, to try and fix the flakiness. I've added an issue link in-code to ensure this is removed when the underlying bug is fixed. |
|
This reverts commit 6dca5a7. Signed-off-by: Simeon Widdis <sawiddis@amazon.com>
* Replace refresh with wait for creation Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Remove unused variable Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Re-add refresh/reload with issue ref Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Revert "Re-add refresh/reload with issue ref" This reverts commit 6dca5a7. Signed-off-by: Simeon Widdis <sawiddis@amazon.com> --------- Signed-off-by: Simeon Widdis <sawiddis@amazon.com> (cherry picked from commit 8014ae0)
* Replace refresh with wait for creation Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Remove unused variable Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Re-add refresh/reload with issue ref Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Revert "Re-add refresh/reload with issue ref" This reverts commit 6dca5a7. Signed-off-by: Simeon Widdis <sawiddis@amazon.com> --------- Signed-off-by: Simeon Widdis <sawiddis@amazon.com> (cherry picked from commit 8014ae0)
* Replace refresh with wait for creation Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Remove unused variable Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Re-add refresh/reload with issue ref Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Revert "Re-add refresh/reload with issue ref" This reverts commit 6dca5a7. Signed-off-by: Simeon Widdis <sawiddis@amazon.com> --------- Signed-off-by: Simeon Widdis <sawiddis@amazon.com> (cherry picked from commit 8014ae0) Co-authored-by: Simeon Widdis <sawiddis@amazon.com>
* Replace refresh with wait for creation Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Remove unused variable Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Re-add refresh/reload with issue ref Signed-off-by: Simeon Widdis <sawiddis@amazon.com> * Revert "Re-add refresh/reload with issue ref" This reverts commit 6dca5a7. Signed-off-by: Simeon Widdis <sawiddis@amazon.com> --------- Signed-off-by: Simeon Widdis <sawiddis@amazon.com> (cherry picked from commit 8014ae0) Co-authored-by: Simeon Widdis <sawiddis@amazon.com>
Description
Since notebooks are still flaky on notebook creation, even with refresh logic added (see #1250), I think the reason the tests are still failing is because notebook creation is flaky in some index refresh race condition scenarios. This PR refactors the notebook creation to drop the refresh attempt and only check for a successful creation message, on the assumption that notebooks should have a functional requirement to always show a valid notebook after stating a successful creation.
I'm not sure this fixes the flaky tests in CI (still struggling to understand the root cause and get exact repro steps), but in local testing this passed 10 consecutive runs (the old version failed after 6 runs and a version with both parts fails almost every run). This should also pass the ball out of the testing repo's court, I've created a corresponding issue: opensearch-project/dashboards-observability#1822.
Also needs backport to 2.x and main.
Issues Resolved
N/A
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.