Skip to content

Windows ngcc infinite loop and tests under windows - #30297

Closed
alan-agius4 wants to merge 6 commits into
angular:masterfrom
alan-agius4:windows-ngcc-integration-tests
Closed

alan-agius4 wants to merge 6 commits into
angular:masterfrom
alan-agius4:windows-ngcc-integration-tests

Conversation

@alan-agius4

@alan-agius4 alan-agius4 commented May 7, 2019 •

Copy link
Copy Markdown
Contributor

fix(ivy): handle windows drives correctly

At the moment the module resolver will end up in an infinite loop in Windows because we are assuming that the root directory is always / however in windows this can be any drive letter example c:/ or d:/ etc...

With this change we also resolve the drive letter in windows, when using AbsoluteFsPath.from for consistence so under /foo will be converted to c:/foo this is also needed because of relative paths with different drive letters.

This also fixes these test targets

//packages/compiler-cli/ngcc/test:integration                            PASSED in 90.9s                                                                                                  
//packages/compiler-cli/ngcc/test:test                                        PASSED in 5.2s      

Partially addresses #29785

@alan-agius4 alan-agius4 added hotlist: windows-support action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews action: review The PR is still awaiting reviews from at least one requested reviewer area: core Issues related to the framework runtime labels May 7, 2019
@ngbot ngbot Bot added this to the needsTriage milestone May 7, 2019
@alan-agius4
alan-agius4 marked this pull request as ready for review May 7, 2019 08:08
@alan-agius4
alan-agius4 requested review from a team May 7, 2019 08:08
@alan-agius4 alan-agius4 removed the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label May 7, 2019
@alan-agius4 alan-agius4 changed the title Windows ngcc integration tests Windows ngcc infinite loop and tests under windows May 7, 2019
@alan-agius4 alan-agius4 added comp: ivy target: major This PR is targeted for the next major release labels May 7, 2019
@alan-agius4

Copy link
Copy Markdown
Contributor Author

Supersedes #30212 since there are new commits to fix the integration tests in Windows

@alan-agius4

Copy link
Copy Markdown
Contributor Author

//cc @meteorcloudy

Comment thread .codefresh/codefresh.yml Resolved

@gkalpak gkalpak left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

One minor comment. LGTM otherwise.

@devversion devversion left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's go ahead and delete fromUnchecked if it's not used.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It still used in a couple of places.

@alxhub

alxhub commented May 7, 2019

Copy link
Copy Markdown
Member

Presubmit

@alan-agius4 alan-agius4 added action: presubmit The PR is in need of a google3 presubmit and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels May 7, 2019
@alexeagle

Copy link
Copy Markdown
Contributor

presubmit

@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note and removed action: presubmit The PR is in need of a google3 presubmit labels May 13, 2019
At the moment the module resolver will end up in an infinite loop in Windows because we are assuming that the root directory is always `/` however in windows this can be any drive letter example `c:/` or `d:/` etc...

With this change we also resolve the drive letter in windows, when using `AbsoluteFsPath.from` for consistence so under `/foo` will be converted to `c:/foo` this is also needed because of relative paths with different drive letters.
```
//packages/compiler-cli/ngcc/test:test
```

Partially addresses #29785
```
//packages/compiler-cli/ngcc/test:integration
```

Partially addresses #29785
@alxhub alxhub closed this in 3a7bfc7 May 13, 2019
alxhub pushed a commit that referenced this pull request May 13, 2019
```
//packages/compiler-cli/ngcc/test:test
```

Partially addresses #29785

PR Close #30297
alxhub pushed a commit that referenced this pull request May 13, 2019
```
//packages/compiler-cli/ngcc/test:integration
```

Partially addresses #29785

PR Close #30297
@alan-agius4
alan-agius4 deleted the windows-ngcc-integration-tests branch May 13, 2019 18:33
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
At the moment the module resolver will end up in an infinite loop in Windows because we are assuming that the root directory is always `/` however in windows this can be any drive letter example `c:/` or `d:/` etc...

With this change we also resolve the drive letter in windows, when using `AbsoluteFsPath.from` for consistence so under `/foo` will be converted to `c:/foo` this is also needed because of relative paths with different drive letters.

PR Close angular#30297
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
```
//packages/compiler-cli/ngcc/test:test
```

Partially addresses angular#29785

PR Close angular#30297
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
```
//packages/compiler-cli/ngcc/test:integration
```

Partially addresses angular#29785

PR Close angular#30297
@angular-automatic-lock-bot

Copy link
Copy Markdown

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 15, 2019
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 area: core Issues related to the framework runtime cla: yes merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants