-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add server tests to travis #32
Comments
That would be really cool to include the test in at least one of them, perhaps robot test first if that's easier. It might make a lot of server side testing easier if we later want to increase the converge of testing, or adding new features on solr side. |
Currently it looks like the the download takes a long time, althought he problem may be in the script. We can get around Travis choking the build if it's longer than 10 minutes, although I'd rather have our builds be shorter. |
Right, the downloading of whole solr dist might be a waste of time and bandwidth for every build. Maybe we can skip the server test in travis for now? The "robot" seems enough to cover those tests. |
I think the way to approach this is to include the solr distribution in our repo |
Was the solr dist download the blocking issue? -----Original Message----- I think the way to approach this is to include the solr distribution in our repo — |
Yes. Maybe hosting on S3 would be faster somehow too but putting it on the On Tue, Sep 22, 2015 at 6:49 PM, Lianyi [email protected] wrote:
|
The logic to start server (running
make
) could happen in.travis.yml
or within a robot test.This will add some time to the tests as it takes some time to download solr, I don't think that we will hit memory limits on travis.
Related to #17
The text was updated successfully, but these errors were encountered: