archive/rsnext

Fork 0

Commit graph

Author	SHA1	Message	Date
JJ Kasper	53d017d3f1	Parallelize dev/start flake detection (#63954 ) Since we're re-running tests a few times and in both modes this can take a while ([related run](https://github.com/vercel/next.js/actions/runs/8514892757/job/23321431099?pr=56995)), so this parallelizes by separating dev/prod into separate jobs. Closes NEXT-2975	2024-04-02 11:40:27 -07:00
JJ Kasper	2359d3d275	Add job to test flakiness of added/changed tests (#63943 ) To help detect when newly added/changed assertions are flakey this adds a job to our build and test workflow to re-run them 3 times. If the changed test is an E2E test it will re-run in both development and production mode to ensure it's not flakey specifically in one of those modes. Test run with changed test can be seen here https://github.com/vercel/next.js/actions/runs/8511797725/job/23312158523?pr=63943 Closes NEXT-2973	2024-04-01 20:15:43 +00:00

Author

SHA1

Message

Date

JJ Kasper

53d017d3f1

Parallelize dev/start flake detection (#63954 )

Since we're re-running tests a few times and in both modes this can take
a while ([related
run](https://github.com/vercel/next.js/actions/runs/8514892757/job/23321431099?pr=56995)),
so this parallelizes by separating dev/prod into separate jobs.

Closes NEXT-2975

2024-04-02 11:40:27 -07:00

JJ Kasper

2359d3d275

Add job to test flakiness of added/changed tests (#63943 )

To help detect when newly added/changed assertions are flakey this adds
a job to our build and test workflow to re-run them 3 times. If the
changed test is an E2E test it will re-run in both development and
production mode to ensure it's not flakey specifically in one of those
modes.

Test run with changed test can be seen here
https://github.com/vercel/next.js/actions/runs/8511797725/job/23312158523?pr=63943

Closes NEXT-2973

2024-04-01 20:15:43 +00:00

2 commits