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

Intermittent test hang when running e2e integration tests locally #832

Closed
c-mcraeolson opened this issue Jun 1, 2022 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@c-mcraeolson
Copy link
Collaborator

Preflight Checklist

  • [ x] I have read the Contributing Guidelines for this project.
  • [ x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

  • Operating System:
    • macOS 12.4
  • Browser:
    • Chrome

Expected Behavior

I expect the integration tests to run consistently, or have a clear error if something has changed to cause them to fail.

Actual Behavior

Perhaps 1/3 of the time, the integration tests simply hang right after starting.

The hang, when it occurs, always happens at the same place - right after printing "Cloud Carbon Footprint" - and (in a headed test) before the page actually loads (the testCafe "connected" icon is still in the center of the page.)

This appears to be an error state, not purely random chance - either it's happening every time, or it isn't happening at all. Sometimes simply closing and re-opening VSCode will fix it.

It seems to be some kind of connection issue with TestCafe, it may be a bug on their side or some small configuration issue with our site (I did some googling for similar errors and found their team responding to somewhat similar things but no smoking gun).

To Reproduce

Unfortunately it's inconsistent. When it occurs for me it's on normal test runs, so just
$ yarn headless
or
$ yarn headed
from packages/integration tests.

Additional Information

On my system there is also a similar intermittent hang at the end of the Talisman flow, after it has run all test suites, including the integration tests. In the cases where this error does occur, it seems to trigger the error state described in this ticket.

I reported this it TestCafe's team here, so they may have suggestions.
https://stackoverflow.com/questions/72465806/intermittent-testcafe-hang-issue

© 2021 Thoughtworks, Inc.

@c-mcraeolson c-mcraeolson added the bug Something isn't working label Jun 1, 2022
@c-mcraeolson c-mcraeolson added this to Backlog in Cloud Carbon Footprint project board via automation Jun 1, 2022
@tinamthomas
Copy link
Contributor

tinamthomas commented Nov 4, 2022

I believed this is due to an issue mentioned on jeffbski/wait-on#116. Looking into it as part of trying to get the integration tests run on CI (#818)

@4upz 4upz moved this from Backlog to In Progress in Cloud Carbon Footprint project board Nov 7, 2022
tinamthomas added a commit to tinamthomas/cloud-carbon-footprint that referenced this issue Nov 7, 2022
tinamthomas added a commit to tinamthomas/cloud-carbon-footprint that referenced this issue Nov 9, 2022
@mvaltas mvaltas moved this from In Progress to Done in Cloud Carbon Footprint project board Nov 10, 2022
@mvaltas mvaltas closed this as completed Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants