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

[WIP] Update for timeout issue for playwright test errors #1601

Closed

Conversation

lakshmimsft
Copy link
Contributor

  1. Bringing back check to ensure all pods are up before playwright test is invoked and
  2. Increasing timeouts.
    (We can run this on the pipeline to see it's effects, if not helpful, we can revert it back).

Fixes: #1592

@lakshmimsft lakshmimsft changed the title Attempt to improve timeout issue for playwright test errors Update for timeout issue for playwright test errors Jul 12, 2024
@lakshmimsft lakshmimsft force-pushed the lakshmimsft/timeoutissue branch 3 times, most recently from 05e38f9 to acc56ec Compare July 12, 2024 22:17
@lakshmimsft lakshmimsft changed the title Update for timeout issue for playwright test errors [WIP] Update for timeout issue for playwright test errors Jul 12, 2024
@lakshmimsft lakshmimsft force-pushed the lakshmimsft/timeoutissue branch 5 times, most recently from 609054e to e1d13d6 Compare July 13, 2024 00:17
Comment on lines +269 to +275
- name: Wait for all pods to be ready
if: steps.gen-id.outputs.RUN_TEST == 'true'
id: wait-for-pods
run: |
namespace="${{ matrix.env }}-${{ matrix.app }}"
label="radapp.io/application=${{ matrix.app }}"
kubectl rollout status deployment -l $label -n $namespace --timeout=90s
Copy link
Collaborator

Choose a reason for hiding this comment

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

We don't need this because rad deploy already waits for all pods to be ready. We discussed this with @rynowak.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ideally we don't need this 😉. If we're inserting waits in random places it can mask bugs.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, i had seen the comment in an earlier PR where this isn't needed. I was curious what the output of this would be now since the endpoint isn't currently loading. no intention to merge this in.

@lakshmimsft
Copy link
Contributor Author

closing this for now. so, far determined that it's not a timeout issue. endpoint is not reachable. local debugging is needed for further debugging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Scheduled Tests: Run Playwright tests failing while Navigating to the endpoint: http://localhost .
3 participants