[turbopack] Enable debug assertions in CI (#80739)
## Enable debug assertions in CI ### What? Build using `--profile release-with-assertions` for all tests in CI. A previous PR (https://github.com/vercel/next.js/pull/80511) enabled them for unit tests, this completes the effort for e2e tests run in CI. There is one exception. The production tests currently have a failing assertion for duplicate modules, so a new env var (`TURBOPACK_TEMP_DISABLE_DUPLICATE_MODULES_CHECK`) is introduced to disable that exact check to allow this to be landed. ### Why? Debug assertions help catch bugs early by validating assumptions in the code. By enabling them in tests, we can improve quality ### How? - Added a new `rustBuildProfile` parameter to the reusable build workflow to control the build profile - Created a new `build-native-release-with-assertions` script in next-swc to set the cargo profile - Updated the turbopack production tests to set the opt out variable Part-of PACK-4578
Showing
Please
register
or
sign in
to comment