mongoid-geospatial
mongoid-geospatial copied to clipboard
Updated travis.yml file for better test coverage
Seeing how Travisl will run with this configuration
Ok, this failed because of when all of Github failed, trying to get the tests to run again
1 Warning | |
---|---|
:warning: | Unless you’re refactoring existing code, please update CHANGELOG.md. |
Here's an example of a CHANGELOG.md entry:
* [#69](https://github.com/mongoid/mongoid-geospatial/pull/69): Updated travis.yml file for better test coverage - [@camiloforero](https://github.com/camiloforero).
Generated by :no_entry_sign: danger
Coverage remained the same at 95.724% when pulling 52446aacd0a3ffe8f799a8648bc3a4994e0080a3 on camiloforero:master into 9d25a5a3b93e33147ca0824dfe3d88c9278824d1 on mongoid:master.
Coverage remained the same at 95.724% when pulling 52446aacd0a3ffe8f799a8648bc3a4994e0080a3 on camiloforero:master into 9d25a5a3b93e33147ca0824dfe3d88c9278824d1 on mongoid:master.
Coverage remained the same at 95.724% when pulling 52446aacd0a3ffe8f799a8648bc3a4994e0080a3 on camiloforero:master into 9d25a5a3b93e33147ca0824dfe3d88c9278824d1 on mongoid:master.
Coverage remained the same at 95.724% when pulling 52446aacd0a3ffe8f799a8648bc3a4994e0080a3 on camiloforero:master into 9d25a5a3b93e33147ca0824dfe3d88c9278824d1 on mongoid:master.
I've seen similar failures elsewhere. I think newer mongodb/mongoid created a newer index version. I didn't get a chance to track that down, would be nice to pinpoint what exactly happen and I think the fix is just to change the specs.
Do we want to resurrect this? You have my attention @camiloforero.