Skip to content

2e2 tests are failing on forked repo #2465

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

Closed
ruchernchong opened this issue Jan 25, 2023 · 2 comments
Closed

2e2 tests are failing on forked repo #2465

ruchernchong opened this issue Jan 25, 2023 · 2 comments
Labels
bug Something isn't working.

Comments

@ruchernchong
Copy link

Describe the bug

As per the screenshot below, the test is failing on a forked repo.

Expected behaviour

Test should pass just like the repo from upstream.

Screenshots / Live demo link

image

Additional context

No response

@rickstaa
Copy link
Collaborator

rickstaa commented Jan 25, 2023

Describe the bug

As per the screenshot below, the test is failing on a forked repo.

Expected behaviour

Test should pass just like the repo from upstream.

Screenshots / Live demo link

image

Additional context

No response

@ruchernchong don't worry; that action is a double-check that the APIs work when a change is deployed to Vercel. It only matters if you are doing development and want to merge a change into the upstream. More importantly, in this case, the Wakatime API timed out. This happens from time to time. The problem will likely go away when you re-run the action.

@ruchernchong
Copy link
Author

Describe the bug

As per the screenshot below, the test is failing on a forked repo.

Expected behaviour

Test should pass just like the repo from upstream.

Screenshots / Live demo link

image

Additional context

No response

@ruchernchong don't worry; that action is a double-check that the APIs work when a change is deployed to Vercel. It only matters if you are doing development and want to merge a change into the upstream. More importantly, in this case, the Wakatime API timed out. This happens from time to time. The problem will likely go away when you re-run the action.

Got it. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

2 participants