Skip to content
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

ci: re-enable chrome mobile tests on android #32447

Conversation

devversion
Copy link
Member

@devversion devversion commented Sep 2, 2019

With 63dff9c, we temporarily disabled the chrome mobile
tests on Android because the launched browsers weren't
able to load the karma page through the tunnel.

The Saucelabs support responded to a ticket that we opened and said that
there were issues with those browsers which are now resolved.

With 63dff9c, we temporarily disabled
the chrome mobile tests on Android because the launched browsers weren't
able to load the karma page through the tunnel.

The Saucelabs support responded to a ticket that we opened and said that
there were issues with those browsers which are now resolved.
@ngbot ngbot bot added this to the needsTriage milestone Sep 2, 2019
@devversion devversion marked this pull request as ready for review Sep 2, 2019
Copy link
Member

@josephperrott josephperrott left a comment

LGTM

@ngbot

This comment was marked as off-topic.

@devversion
Copy link
Member Author

@devversion devversion commented Sep 2, 2019

Caretaker note: I have absolutely no idea where the pullapprove check comes from. I opened up a discussion about this in the dev-infra channel. PR should be good to go anyway.

kara
kara approved these changes Sep 2, 2019
mhevery added a commit that referenced this issue Sep 3, 2019
With 63dff9c, we temporarily disabled
the chrome mobile tests on Android because the launched browsers weren't
able to load the karma page through the tunnel.

The Saucelabs support responded to a ticket that we opened and said that
there were issues with those browsers which are now resolved.

PR Close #32447
sabeersulaiman added a commit to sabeersulaiman/angular that referenced this issue Sep 6, 2019
With 63dff9c, we temporarily disabled
the chrome mobile tests on Android because the launched browsers weren't
able to load the karma page through the tunnel.

The Saucelabs support responded to a ticket that we opened and said that
there were issues with those browsers which are now resolved.

PR Close angular#32447
arnehoek added a commit to arnehoek/angular that referenced this issue Sep 26, 2019
With 63dff9c, we temporarily disabled
the chrome mobile tests on Android because the launched browsers weren't
able to load the karma page through the tunnel.

The Saucelabs support responded to a ticket that we opened and said that
there were issues with those browsers which are now resolved.

PR Close angular#32447
@angular-automatic-lock-bot
Copy link

@angular-automatic-lock-bot angular-automatic-lock-bot bot commented Oct 4, 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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants