Skip to content

build: run saucelabs and browserstack tests with ivy #18276

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

Conversation

devversion
Copy link
Member

We recently regressed when we switched to the auto-generated
SystemJS configuration in terms of how those legacy karma tests
run. Previously they ran with Ivy, but currently they run with view
engine. We should switch them back to Ivy since Ivy is the default in
version 9.

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Jan 24, 2020
@devversion devversion requested a review from a team as a code owner January 24, 2020 09:59
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 24, 2020
@jelbourn
Copy link
Member

Looks like some CI failures

We recently regressed when we switched to the auto-generated
SystemJS configuration in terms of how those legacy karma tests
run. Previously they ran with Ivy, but currently they run with view
engine. We should switch them back to Ivy since Ivy is the default in
version 9.
@devversion devversion force-pushed the build/run-saucelabs-browserstack-tests-with-ivy branch from 0dd5bdb to 38ff823 Compare January 24, 2020 20:47
@devversion
Copy link
Member Author

@jelbourn Fixed.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 25, 2020
@jelbourn jelbourn merged commit 27498ea into angular:master Jan 25, 2020
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
We recently regressed when we switched to the auto-generated
SystemJS configuration in terms of how those legacy karma tests
run. Previously they ran with Ivy, but currently they run with view
engine. We should switch them back to Ivy since Ivy is the default in
version 9.
@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 Feb 25, 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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants