You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bazel schematic builds prod bundle for ng test #30191
ng test should just run the unit tests, not run rollup and terser to bundle the production app.
(this happens because we do bazel test //src/... which also builds all the buildable things. Adding tags=['manual'] on targets that are only needed for production is one way to solve it)
Even simpler fix is for the "test" builder to have "options: { "targetLabel": "//src/app/..." } so it skips all top-level targets. This assumes there aren't any unit tests in the //src package.
Activity
alexeagle commentedon Apr 29, 2019
Even simpler fix is for the "test" builder to have
"options: { "targetLabel": "//src/app/..." }so it skips all top-level targets. This assumes there aren't any unit tests in the //src package.fix(bazel): ng test should run specific ts_web_test_suite (#30526)
fix(bazel): ng test should run specific ts_web_test_suite (angular#30526
angular-automatic-lock-bot commentedon Sep 15, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
fix(bazel): ng test should run specific ts_web_test_suite (angular#30526