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

E2E - Flaky test? #3755

Closed
Tracked by #3682
preschian opened this issue Aug 16, 2022 · 3 comments · Fixed by #3759
Closed
Tracked by #3682

E2E - Flaky test? #3755

preschian opened this issue Aug 16, 2022 · 3 comments · Fixed by #3759
Assignees
Labels

Comments

@preschian
Copy link
Member

seems like there is some flaky test. for example, try to open test jobs in this pipeline https://github.com/kodadot/nft-gallery/actions/runs/2862034445
Screen Shot 2022-08-16 at 21 21 07

sometimes, it can be reproducible on local also. try to retry the test several times. there is some test that needs several attempts to succeed (marked with yellow colour)
Screen Shot 2022-08-16 at 21 20 02

for a temporary fix, try to retry your pipeline in case you get an error.

it would be great if the issue was resolved. possible fix (maybe):

  • increase the timeout from 4s to 10s?
  • increase retries attempts from 2 to 3?
@yangwao
Copy link
Member

yangwao commented Aug 16, 2022

why it needs more than 4000ms?
let's try to raise it 10s, it depends on the CPU of the pipeline to render something?

@preschian
Copy link
Member Author

why it needs more than 4000ms? let's try to raise it 10s, it depends on the CPU of the pipeline to render something?

tbh not sure, need further investigation. let me check it first 🙏🏻

@preschian preschian self-assigned this Aug 16, 2022
@kodabot
Copy link
Collaborator

kodabot commented Aug 16, 2022

ASSIGNED - @preschian 🔒 LOCKED -> Thursday, August 18th 2022, 02:41:52 UTC -> 36 hours

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

Successfully merging a pull request may close this issue.

3 participants