-
Notifications
You must be signed in to change notification settings - Fork 62
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
The service "test.client" has a dependency on a non-existent service "test.client.history". #88
Comments
Are there any other packages being updated as well? Could you provide a stacktrace (run Behat with We're using SymfonyExtension v2.0.8 with Symfony v4.3.3 in Sylius builds and it's passing on Travis: https://travis-ci.org/Sylius/Sylius/jobs/566377307 |
I've done a bounce of updates but already in dev (where every test is fine). Here's the stack trace.
I've checked Sylius in order to find if you were using the same version but, as long as |
Debug shows how with old extension (symfony2extension) and symfony 4.3.3, |
@pamil if I do Edit: my fault, there's an extension so is perfectly legit for this bundle to be loaded while compiling the container. |
@pamil my bad, the previous version of symfony was 4.1 not 4.2. |
A little update for this: I've managed to let it work but still not sure why.
As soon as I changed it to an alias like (removing the declaration under
everything works. So it must be something in Symfony >= 4.2 or in this extension or in the combination of both that mess up the things. Any clues? |
@DonCallisto I think your issue is that you don't have Please have a look at the method
specifically the following lines: if (!empty($config['test'])) {
$loader->load('test.xml');
if (!class_exists(AbstractBrowser::class)) {
$container->removeDefinition('test.client');
}
} Notice that the definition 'test.client' is removed if it cannot find The class |
@siment I have that bundle installed (and enabled) otherwise I won't be able to do what I've done in #88 (comment) |
Right... I missed that part. Wish I could help you more. Good luck. |
Does this error still happen with the newest Symfony (4.4.*)? |
@pamil I will try with Symfony 4.4.* and previous configuration, hopefully, this week end. |
@pamil sorry for being late on this. Just updated the project to Symfony4.4.* and the issue is still there. |
I confirmed, still problem with 4.4. |
Build failures on Sylius look connected with this issue: Sylius/Sylius#11029 |
I think that adding If makes sense to you, I'll open a PR. |
@DonCallisto sounds good, feel free to send a PR. Is there any way we could also test it to avoid regressions in the future? |
@pamil Maybe check if |
Makes sense! Let's first create a failing test and then add the fix to make sure that's the case. Thanks a lot! |
Hi,
after upgrading symfony version from 4.2 to 4.3 (actually 4.3.3) I have this error shown when I try to run any behat test.
I think that has something to do with this extension as if I try with a different extension - wich I trying to get rid of; is symfony2extension - everything works fine.
Moreover with symfony 4.2 and this extension, everything is fine.
The error is shown in the title.
The text was updated successfully, but these errors were encountered: