-
Notifications
You must be signed in to change notification settings - Fork 91
test: skip tests #3116
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
test: skip tests #3116
Conversation
{ | ||
"file": "test/e2e/app-dir/sub-shell-generation-middleware/sub-shell-generation-middleware.test.ts", | ||
"reason": "Checking Vercel specific x-vercel-cache header", | ||
"tests": ["middleware-static-rewrite should eventually result in a cache hit"] | ||
} |
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.
This was recently added
📊 Package size report No changes
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
{ | ||
"file": "test/e2e/app-dir/rsc-redirect/rsc-redirect.test.ts", | ||
"reason": "page.waitForLoadState('networkidle') not resolving", | ||
"tests": [ | ||
"rsc-redirect /old-about -> /about (ppr: false, segmentCache: true) uses prefetched, redirected URL in the navigation, as opposed to the href in the link", | ||
"rsc-redirect /old-about -> /about (ppr: false, segmentCache: false) uses prefetched, redirected URL in the navigation, as opposed to the href in the link" | ||
] | ||
}, |
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.
This test failure or rather timeout is confusing. Test get stuck on
page.waitForLoadState('networkidle')
usage of which is strongly discouraged:
'networkidle' - DISCOURAGED wait until there are no network connections for at least 500 ms. Don't use this method for testing, rely on web assertions to assess readiness instead.
The test does pass if I replace that with couple seconds of just sleeping, but that's not something we can change so skipping it here.
I did try to debug this test on what keeps it stuck, but all the initiated requests finish and I so no network activity that could be keeping it stuck 🤷
Description
Skip tests that are checking Vercel specific response header OR ones that previously passed, but no longer do after #3100 excluded lambda from handling 404s for
_next/static