Skip to content

Error when running the e2e for app-router (Fetch cache) #328

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.

Sign up for GitHub

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

Jump to bottom
Closed
vicb opened this issue Feb 3, 2025 · 2 comments · Fixed by #364
Closed

Error when running the e2e for app-router (Fetch cache) #328

vicb opened this issue Feb 3, 2025 · 2 comments · Fixed by #364
Assignees
@dario-piotrowicz
Labels
bug Something isn't working

Comments

@vicb
Copy link
Contributor

vicb commented Feb 3, 2025

@dario-piotrowicz I am seeing this error when running pnpm -F app-router e2e (locally and on the CI).

Do you have any idea of the root cause?

Thanks!
@vicb vicb added the bug Something isn't working label Feb 3, 2025
@dario-piotrowicz dario-piotrowicz mentioned this issue Feb 3, 2025
Merged
@dario-piotrowicz
Copy link
Contributor

No idea, as you can see that passed in the PR in which I enabled the app-router e2es: #314 😕

I'll have a look

@james-elicx
Copy link
Collaborator

I've found it to be a bit intermittent

This was referenced Feb 4, 2025
Closed
Closed
@vicb vicb changed the title Error when running the e2e for app-router Error when running the e2e for app-router (Fetch cache) Feb 5, 2025
This was referenced Feb 5, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dario-piotrowicz dario-piotrowicz

Labels
bug Something isn't working
Projects
`@opennextjs/cloudflare` prioritization and tracking
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: make sure that fetch cache sets are properly awaited opennextjs/opennextjs-cloudflare
3 participants
@vicb @james-elicx @dario-piotrowicz