-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
ci(actions): report failed --turbo next.js tests #3350
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
8 Ignored Deployments
|
6eee95b
to
60e94a3
Compare
Benchmark for 6c203b1Click to view benchmark
|
1ee7b6f
to
983a449
Compare
Benchmark for 8e98fc7
Click to view full benchmark
|
🟢 CI successful 🟢Thanks |
d6d0787
to
b80c828
Compare
b80c828
to
d9c1c18
Compare
Failing next.js integration test suitesCommit: b264321
Expand output● ReactRefreshLogBox › Node.js builtins
● ReactRefreshLogBox › Module not found
● ReactRefreshLogBox › Module not found (empty import trace)
● ReactRefreshLogBox › Module not found (missing global CSS)
Expand output● browser-shallow-navigation › should render the correct page
Expand output● 404 Page Support with _app › dev mode › should not show pages/404 GIP error if _app has GIP
Expand output● ReactRefreshLogBox app › Node.js builtins
● ReactRefreshLogBox app › Module not found
● ReactRefreshLogBox app › Module not found empty import trace
● ReactRefreshLogBox app › Module not found missing global CSS
Expand output● app dir rendering › should serve app/page.server.js at /
● app dir rendering › SSR only › should run data in layout and page
● app dir rendering › SSR only › should run data fetch in parallel
● app dir rendering › static only › should run data in layout and page
● app dir rendering › static only › should run data in parallel during development
● app dir rendering › ISR › should revalidate the page when revalidate is configured
Expand output● Default 404 Page with custom _error › dev mode › should respond to 404 correctly
● Default 404 Page with custom _error › dev mode › should render error correctly
● Default 404 Page with custom _error › dev mode › should render index page normal
Expand output● ReactRefreshLogBox › Node.js builtins
● ReactRefreshLogBox › Module not found
● ReactRefreshLogBox › Module not found (empty import trace)
● ReactRefreshLogBox › Module not found (missing global CSS)
Expand output● browser-shallow-navigation › should render the correct page
Expand output● 404 Page Support with _app › dev mode › should not show pages/404 GIP error if _app has GIP
Expand output● ReactRefreshLogBox app › Node.js builtins
● ReactRefreshLogBox app › Module not found
● ReactRefreshLogBox app › Module not found empty import trace
● ReactRefreshLogBox app › Module not found missing global CSS
Expand output● app dir rendering › should serve app/page.server.js at /
● app dir rendering › SSR only › should run data in layout and page
● app dir rendering › SSR only › should run data fetch in parallel
● app dir rendering › static only › should run data in layout and page
● app dir rendering › static only › should run data in parallel during development
● app dir rendering › ISR › should revalidate the page when revalidate is configured
Expand output● Default 404 Page with custom _error › dev mode › should respond to 404 correctly
● Default 404 Page with custom _error › dev mode › should render error correctly
● Default 404 Page with custom _error › dev mode › should render index page normal
|
616aa40
to
da09da5
Compare
Benchmark for 41216bbClick to view benchmark
|
Benchmark for 4269545Click to view benchmark
|
Benchmark for a6a4308Click to view benchmark
|
Benchmark for 7c71cd4Click to view benchmark
|
Benchmark for b264321Click to view benchmark
|
### Features - vercel/turborepo#3409 ### Bug Fixes - vercel/turborepo#3399 - vercel/turborepo#3412 ### Chore - vercel/turborepo#3398 - vercel/turborepo#3391 - vercel/turborepo#3350
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.
forgot to submit
|
||
runs: | ||
using: node16 | ||
main: index.js |
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.
Maybe put it in dist/index.js
like the other action I added
"private": true, | ||
"main": "src/index.js", | ||
"scripts": { | ||
"pack": "ncc -o . build src/index.js" |
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.
Also maybe build on prepare
like my action and add it to the pnpm workspace
Closes WEB-168.
This PR changes the behavior of next.js integration test in this repo to run everything with
--turbo
by default, instead of manually opt in per each PR. Since current next.js integration tests are expected to fail with turbopack, PR adds changesDo not fail CI when next.js integration test fails
So we can keep CI checker green for the daily workflow
Report failed tests in the PR comment
Instead, report failed tests in the comment, like ci(actions): report failed --turbo next.js tests #3350 (comment)
This is largely similar to what next.js upstream does for failing report, but does not use exact same webhook since the way CI pipeline sets up is bit different so we can't use it out of the box. However, the logic in the custom action is short & straightforward enough to keep internally.
One thing to note is this report uses default automatic github auth token (user
github-actions
bot). This means report comment will not be created if PR is created from fork, but I expect that's acceptable limitation.There maybe some improvements we want to add, like diff-between-main but probably not a high priority & maybe we can fix all the turbopack faster than having those.