-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
chore: fix Onboarding/CreateNewApp flaky test #21347
Conversation
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4401296678. |
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4401820992. |
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4403954534. |
The following are new failures, please fix them before merging the PR
|
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4404919810. |
/ok-to-test |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4414258959. |
_.homePage.CreateNewWorkspace(workspaceName); | ||
_.homePage.CreateAppInWorkspace(workspaceName); //Since welcome tour always creates app in 1st workspace available | ||
_.homePage.NavigateToHome(); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We aren't really using the workspaceName
variable anywhere in the test so have removed this . Removing this also seems to have stopped the 503 errors not sure why though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this does not solve the issue. I add the new workspace creation code as a part of script fix - for 503. Tried adding new workspace, creating new application in it & then try to click on welcome tour. This will not/does not solve the 503.
.click() | ||
.wait(4000); | ||
} | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CloseReconnectDataSourceModal
and clicking on the welcomeTour
are repeated which are not required to run the test, so have removed them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was added since we see the Reconnect modal dialog appearing out of nowhere in this test flow & test failing to click on welcome tour. Removing this also will not solve the 503 issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the reconnect modal does appear then either it is a bug or some issue the fork api on ci. Either ways keeping this is a workaround. I can have a look at it when it happens next time, so far the 4 times we ran it does not seem to have happened.
Yes I don't think it fixes the 503 issue.
/ok-to-test sha=9abd3d2 |
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/4419574598. |
Warning Rate limit exceeded@Nikhil-Nandagopal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 25 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
Description
Test cleanup to remove commands which are not part of the user flow. Have ran the test suite 3 times and it has passed all the time. Not sure about why the 503 happens sometimes
Fixes #21327
Type of change
Checklist:
Dev activity