Skip to content

build: unable to run schematics tests through test script #19230

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

Merged
merged 1 commit into from
May 7, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented May 2, 2020

Fixes not being able to run the schematics tests through yarn test. The logic for resolving the package was correct, but we were appending the wrong target name.

Fixes #19182.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels May 2, 2020
@crisbeto crisbeto requested a review from a team as a code owner May 2, 2020 09:04
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 2, 2020
@devversion devversion added lgtm action: merge The PR is ready for merge by the caretaker labels May 2, 2020
@jelbourn
Copy link
Member

jelbourn commented May 7, 2020

@crisbeto just needs rebase

Fixes not being able to run the schematics tests through `yarn test`. The logic for resolving the package was correct, but we were appending the wrong target name.

Fixes angular#19182.
@crisbeto crisbeto force-pushed the 19182/test-script-schematics branch from 6fd1393 to 5f3f634 Compare May 7, 2020 05:50
@crisbeto
Copy link
Member Author

crisbeto commented May 7, 2020

Rebased.

@jelbourn jelbourn merged commit ecf4105 into angular:master May 7, 2020
jelbourn pushed a commit that referenced this pull request May 7, 2020
Fixes not being able to run the schematics tests through `yarn test`. The logic for resolving the package was correct, but we were appending the wrong target name.

Fixes #19182.
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(build): run-components-test script can't be used for schematics
4 participants