-
Notifications
You must be signed in to change notification settings - Fork 30.4k
[test] Try deflake client-cache.defaults deployment test
#89106
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] Try deflake client-cache.defaults deployment test
#89106
Conversation
Failing test suitesCommit: 0c6e58a | About building and testing Next.js
Expand output● app dir client cache semantics (experimental staleTimes) › static: 180 › prefetch={undefined} - default › should re-use the loading boundary for the custom static override time (3 minutes)
Expand output● runtime prefetching › in a private cache › can completely prefetch a page that uses cookies and no uncached IO ● runtime prefetching › in a private cache › can completely prefetch a page that uses cookies and no uncached IO
Expand output● Test suite failed to run |
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** ✅ -24 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
|
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
f69003a to
0a5b9c5
Compare
…re page only contains `href="/1?timeout=1000"`, causing the test to fail Co-authored-by: devjiwonchoi <devjiwonchoi@gmail.com>
0a5b9c5 to
8fe3a8b
Compare
This deployment test has been failing very recently since the first attempt of [v16.1.5](https://github.com/vercel/next.js/actions/runs/21373599266/attempts/2). Tried deflaking at #87412, but seems to have no effect. This PR adds the test case to the deployment test manifest to unblock sync. Will continue deflaking at this PR at #89106 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=overview&eventStack=&fromUser=true&index=citest&panel=%7B%22queryString%22%3A%22%40test.name%3A%5C%22app%20dir%20client%20cache%20semantics%20%28default%20semantics%29%20prefetch%3D%7Bundefined%7D%20-%20default%20should%20refetch%20the%20full%20page%20after%205%20mins%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%22app%20dir%20client%20cache%20semantics%20%28default%20semantics%29%20prefetch%3D%7Bundefined%7D%20-%20default%20should%20refetch%20the%20full%20page%20after%205%20mins%22%7D%5D%2C%22timeRange%22%3A%7B%22from%22%3A1769209200000%2C%22to%22%3A1769514811691%2C%22live%22%3Afalse%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=1769209200000&end=1769514811691&paused=true) x-ref: [slack thread](https://vercel.slack.com/archives/C02CDC2ALJH/p1769519877570459) Part of https://linear.app/vercel/issue/NAR-719/fix-deploy-tests

No description provided.