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

SoapClient not found #2664

Closed
orklah opened this issue Jan 19, 2020 · 4 comments
Closed

SoapClient not found #2664

orklah opened this issue Jan 19, 2020 · 4 comments

Comments

@orklah
Copy link
Collaborator

orklah commented Jan 19, 2020

Hi,

There are some skipped tests in CI because of SoapClient not being found
https://ci.appveyor.com/project/muglug/psalm/builds/30216882#L24894

I had the same issue at work but I thought it was because of our whacky codebase. Now that I see the same thing here, I wonder what's going on. I checked and SoapClient is indeed in the ClassMap.

Can I do something to fix it?

@psalm-github-bot
Copy link

Hey @orklah, can you reproduce the issue on https://psalm.dev ?

@LeSuisse
Copy link
Contributor

Do you have ext-soap enabled in the environment running Psalm?

@orklah
Copy link
Collaborator Author

orklah commented Jan 20, 2020

Do you have ext-soap enabled in the environment running Psalm?

That could be it, I will check that tomorrow

@orklah
Copy link
Collaborator Author

orklah commented Jan 21, 2020

ext-soap was indeed disabled. I forgot Psalm was using native extensions and not only stubs. There are tests being skipped on appveyor because of missing extension but I'm not sure it's an issue because the tests will pass on other CI tools. I'm closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants