-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Tavern 2.0.0a4 Failures #734
Comments
Is this in a fresh installation in a docker container or something like that? It looks like an issue with caching of an older version. If it's not a fresh installation, can you try completely removing the old version of Tavern and reinstalling 2.0 and try again? |
Yes, it is a fresh install in a docker container. The dockerfile is
In the development environment it's run as part of a docker-compose inside VSCode. The CMD is overridden by a call to bash, and testing is invoked as 'docker exec -t tavern ./tavern_tests/run_tavern_tests.sh ${input:DCP}' |
2.0.0a1 & 2.0.0.a2 work, 2.0.0a3 & 2.0.0.a4 do not. |
I think this is an error on my machine from my leaving old pycache files lying about. Can you try with |
2.0.0a7 does not exhibit this error, but behaves as I reported in #740. I will look at that later. |
In an attempt to circumvent the problem I was having, as reported in #733, I thought I'd give 2.0 a try.
Unfortunately, it didn't get that far, failing at the initial stage:
The text was updated successfully, but these errors were encountered: