-
Notifications
You must be signed in to change notification settings - Fork 92
test: skip after Next.js repo tests #3081
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are failing on this step https://github.com/vercel/next.js/blob/589065d7884456180b991d4bd57da0e5bdb7fbff/test/e2e/app-dir/next-after-app-deploy/index.test.ts#L44-L56 which is shared by all tests in this test suite
Note that if we would run same "dummy" request as one that is done for PPR case, those tests do pass.
The whole thing likely happens because we mark cache entries generated at build time as stale (if they have
revalidate
set to something not permanent):opennextjs-netlify/src/build/content/prerendered.ts
Lines 166 to 167 in 8202a9a
and because of that:
We do have our own e2e tests for next/after that were inspired by this test in https://github.com/opennextjs/opennextjs-netlify/blob/main/tests/e2e/after.test.ts so we will have test coverage for that particular feature still