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

Re-enable and slightly rewrite flaky GeoPoint test. #588

Closed
wants to merge 2 commits into from

Conversation

nlutsenko
Copy link
Contributor

Do not review yet, exists purely to trigger Travis-CI back and forth.

@facebook-github-bot
Copy link

@nlutsenko updated the pull request.

@facebook-github-bot
Copy link

@nlutsenko updated the pull request.

@flovilmart
Copy link
Contributor

this is now failing on: Parse.GeoPoint testing geo max distance large

@nlutsenko
Copy link
Contributor Author

Yup, can see that. Any idea on what is going on? I have no idea on how to debug this at this point :(

@flovilmart
Copy link
Contributor

Not more than you, maybe put a done() on The failure case. Bump the allowed time for processing up? Are those queries hyper slow in mongo? Should we add indexing on all fields?

@drew-gross
Copy link
Contributor

Querying the geo point is when the geo index is created, which could be slow (although I wouldn't expect it to take 10 seconds) Maybe crank up the allowed time to like 10 minutes and add some measurement on how long it takes.

@flovilmart
Copy link
Contributor

The createIndex is 'blocking', is that intended? We should probably do that when app is created or upon the 1st connection in a non-blocking way?

@drew-gross
Copy link
Contributor

Background index creation at either class creation time or field addition time is probably the way to go. However, I believe mongo requires the index before you can do geo queries so if that is in fact the issue with the test, it wouldn't fix it.

@flovilmart
Copy link
Contributor

@drew-gross @nlutsenko with write access to the repo, you can run travis restart that will help instead of open/close. I'm kinda opening/closing all the times ;(

@facebook-github-bot
Copy link

@nlutsenko updated the pull request.

@facebook-github-bot
Copy link

@nlutsenko updated the pull request.

@drew-gross
Copy link
Contributor

https://travis-ci.org/ParsePlatform/parse-server/jobs/111894700 had a failure for trying to create a 2nd geopoint on a class, which seems to me to indicate that it's racing with the teardown from the previous test, which is the one that checks to make sure that saving two geo points fails. The test this diff is investigating was also right after that test before it was disabled.

@nlutsenko
Copy link
Contributor Author

The test this diff is investigating was also right after that test before it was disabled.

M? Not sure I got you... Also, yes, I am investigating the race condition on teardown.

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

Successfully merging this pull request may close these issues.

4 participants