-
Notifications
You must be signed in to change notification settings - Fork 31
test: run Django tests against Spanner emulator #559
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now we can drop parallelize_tests.go
, its binary version, build.sh
and several environment variables. I'm still keeping them in here, until all the things fixed.
As for the transaction commited error, I've pushed a PR with fix in the original Spanner repo:
googleapis/python-spanner#177
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments, but looks like a big improvement over running the django tests against non-emulated spanner.
I'd like to see the tests passing before we merge this, but it looks like that depends on googleapis/python-spanner#177. Did you check that the tests pass using your own fork of python-spanner with this change applied?
@c24t, now we have some Django tests failing because of several problems. |
@c24t, I've got a green light on Django tests. There are still some things to refactor and improve, but I suppose it's not something to block the release. |
@c24t, okay, I've found the place where the But I'm little bit stuck with hitting 950 query args quota. Not sure why this error showed yet (maybe my eyes just soaped, but), everything seems to be set correctly: skips, dependencies, tests things like UPDATE: too many authorisation rules seems to be prepared for tests (they are inserted within a huge bunch into a table) - that's the problem. |
5c104e6
to
4a23973
Compare
@c24t, so, the Django tests on emulator are canceled because of a timeout hit. Seems to me we still need parallelisation, as slow execution problem has not gone with the emulator. |
@c24t, okay, 8 threads seems to be working, but there is a lot of |
…c/python-spanner-django into dj_tests_against_emulator
No description provided.