-
Notifications
You must be signed in to change notification settings - Fork 30.4k
test(resume-data-cache): add x-vercel-cache-status header assertions #89187
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
base: canary
Are you sure you want to change the base?
test(resume-data-cache): add x-vercel-cache-status header assertions #89187
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Verify cache header values (HIT/STALE) in resume-data-cache e2e tests to ensure proper cache behavior during revalidation.
86cd1c9 to
71e4851
Compare
Failing test suitesCommit: 97f28d0 | About building and testing Next.js
Expand output● Test suite failed to run
Expand output● segment cache (revalidation) › refetch visible Form components after cache is revalidated
Expand output● log-file › should capture client logging in log file
Expand output● resume-data-cache › should have consistent data between static and dynamic renders with use cache ● resume-data-cache › should have consistent data between static and dynamic renders with fetch cache |
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles: **432 kB** → **432 kB** ✅ -42 B81 files with content-based hashes (individual files not comparable between builds) Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
|
Add "should have consistent data between static and dynamic renders with fetch cache" test to the failed list. This test relies on x-vercel-cache-status header assertions that only apply in deployment contexts. Related: #89187 https://linear.app/vercel/issue/NAR-719
This deployment test has been failing very recently. This PR adds the test case to the deployment test manifest to unblock sync. Will continue deflaking at this PR at #89187 x-ref: [Datadog](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20%40ci.pipeline.name%3Atest-e2e-deploy-release%20%40ci.pipeline.url%3A%2A%2Fattempts%2F2%20%40test.status%3Afail&agg_m=count&agg_m_source=base&agg_q=%40test.name&agg_q_source=base&agg_t=count¤tTab=history&eventStack=&fromUser=true&index=citest&panel=%7B%22queryString%22%3A%22%40test.name%3A%5C%22resume-data-cache%20should%20have%20consistent%20data%20between%20static%20and%20dynamic%20renders%20with%20fetch%20cache%5C%22%22%2C%22filters%22%3A%5B%7B%22isClicked%22%3Atrue%2C%22source%22%3A%22log%22%2C%22path%22%3A%22test.name%22%2C%22value%22%3A%22resume-data-cache%20should%20have%20consistent%20data%20between%20static%20and%20dynamic%20renders%20with%20fetch%20cache%22%7D%5D%2C%22timeRange%22%3A%7B%22from%22%3A1769520224000%2C%22to%22%3A1769693024000%2C%22live%22%3Atrue%7D%7D&test-detail-history=log_test.status%2Ctimestamp%2Clog_git.branch%2Clog_git.commit.sha%2Clog_test.is_known_flaky&top_n=30&top_o=top&viz=query_table&x_missing=true&start=1769520224360&end=1769693024360&paused=false) Part of https://linear.app/vercel/issue/NAR-719/fix-deploy-tests

No description provided.