-
Notifications
You must be signed in to change notification settings - Fork 2.2k
split tests into two steps, report ok and done separately #3646
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
|
Failing next.js integration test suitesCommit: d0c0f4b Test summary
✅ Fixed tests: ❌ Newly failed tests: Full test report
Expand output● ReactRefresh › can edit a component without losing state ● ReactRefresh › cyclic dependencies
Expand output● Middleware custom matchers › should match source path ● Middleware custom matchers › should match has header ● Middleware custom matchers › should match has query ● Middleware custom matchers › should match has cookie ● Middleware custom matchers › should match has host ● Middleware custom matchers › should match has header value ● Middleware custom matchers › should match has query on client routing ● Middleware custom matchers › should match has cookie on client routing
Expand output● 404 Page Support with _app › dev mode › should not show pages/404 GIP error if _app has GIP
Expand output● Error overlay - editor links › should be possible to open files on RSC build error ● Error overlay - editor links › should be possible to open files on RSC parse error ● Error overlay - editor links › should be possible to open files on module not found error
Expand output● app-dir alias handling › should handle typescript paths alias correctly ● app-dir alias handling › should resolve css imports from outside with src folder presented
Expand output● Handles a broken webpack plugin (precompile) › should render error correctly
Expand output● ReactRefresh › can edit a component without losing state ● ReactRefresh › cyclic dependencies
Expand output● Middleware custom matchers › should match source path ● Middleware custom matchers › should match has header ● Middleware custom matchers › should match has query ● Middleware custom matchers › should match has cookie ● Middleware custom matchers › should match has host ● Middleware custom matchers › should match has header value ● Middleware custom matchers › should match has query on client routing ● Middleware custom matchers › should match has cookie on client routing
Expand output● 404 Page Support with _app › dev mode › should not show pages/404 GIP error if _app has GIP
Expand output● Error overlay - editor links › should be possible to open files on RSC build error ● Error overlay - editor links › should be possible to open files on RSC parse error ● Error overlay - editor links › should be possible to open files on module not found error
Expand output● app-dir alias handling › should handle typescript paths alias correctly ● app-dir alias handling › should resolve css imports from outside with src folder presented
Expand output● Handles a broken webpack plugin (precompile) › should render error correctly |
Benchmark for e2b894fClick to view benchmark
|
Benchmark for d0c0f4bClick to view benchmark
|
| subjob ${{needs.rust_prepare.result}} "Rust prepare" | ||
| subjob ${{needs.rust_lint.result}} "Rust lints" | ||
| subjob ${{needs.rust_check.result}} "Rust checks" | ||
| subjob ${{needs.turbopack_rust_test1.result}} "Turbopack Rust tests (linux)" |
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.
It's weird that this name is different from that of the job itself (Turbopack Rust testing on ubuntu).
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 might move more tests from 2 to 1 when they have faster runners... I think it's more part 1 and 2, instead of linux in particular
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 rename to (blocking) and (non-blocking)?
tknickman
left a comment
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.
Love it, thanks!
This removes some long running tests (mac and windows) from the required PR checks.
Now the CI workflow is split into two parts,
Ok(required) for the required checks andDone(non-blocking) for all checks.The PR comment will show
🟢 CI likely successful 🟢
A few longer running steps are still running, but they should not be considered as blocking.
See workflow summary for details
after the required checks are done.
Once all checks are done, it will be updated to 🟢 CI successful 🟢 or to⚠️ CI failed ⚠️ depending on the full result