Skip to content

test: add local npm registry to failing tests #15173

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
Jul 26, 2019
Merged

test: add local npm registry to failing tests #15173

merged 1 commit into from
Jul 26, 2019

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Jul 26, 2019

No description provided.

@alan-agius4 alan-agius4 added the target: major This PR is targeted for the next major release label Jul 26, 2019
@alan-agius4 alan-agius4 marked this pull request as ready for review July 26, 2019 13:46
@filipesilva filipesilva requested a review from clydin July 26, 2019 15:53
'install',
'-g',
packages['@angular-devkit/schematics-cli'].tar,
'--unsafe-perm',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here for the package name.
Also, is unsafe-perm actually needed?

const dir = await copyAssets(assetName);
process.chdir(dir);
if (!useNpmPackages) {
await useBuiltPackages();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically, no test should be using the built packages directly anymore but this fixes the problem for now.

We should revisit these tests though. Potentially using npx to generate a new project of the appropriate version directly.

@vikerman vikerman merged commit 2299ad4 into angular:master Jul 26, 2019
vikerman pushed a commit that referenced this pull request Jul 29, 2019
@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 Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants