You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. https://travis-ci.org/NCBI-Hackathons/seqr/builds/78597840
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.
-----Original Message-----
From: Mike Panciera [notifications@github.commailto:notifications@github.com]
Sent: Tuesday, September 22, 2015 06:40 PM Eastern Standard Time
To: NCBI-Hackathons/seqr
Cc: Han, Lianyi (NIH/NLM/NCBI) [C]
Subject: Re: [seqr] Add server tests to travis (#32)
I think the way to approach this is to include the solr distribution in our repo
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-142441486.
-----Original Message-----
From: Mike Panciera [notifications@github.com<mailto: notifications@github.com>]
Sent: Tuesday, September 22, 2015 06:40 PM Eastern Standard Time
To: NCBI-Hackathons/seqr
Cc: Han, Lianyi (NIH/NLM/NCBI) [C]
Subject: Re: [seqr] Add server tests to travis (#32)
I think the way to approach this is to include the solr distribution in
our repo
Activity
lianyi commentedon Sep 3, 2015
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.
averagehat commentedon Sep 3, 2015
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.
https://travis-ci.org/NCBI-Hackathons/seqr/builds/78597840
lianyi commentedon Sep 4, 2015
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.
averagehat commentedon Sep 22, 2015
I think the way to approach this is to include the solr distribution in our repo
lianyi commentedon Sep 22, 2015
Was the solr dist download the blocking issue?
-----Original Message-----
From: Mike Panciera [notifications@github.commailto:notifications@github.com]
Sent: Tuesday, September 22, 2015 06:40 PM Eastern Standard Time
To: NCBI-Hackathons/seqr
Cc: Han, Lianyi (NIH/NLM/NCBI) [C]
Subject: Re: [seqr] Add server tests to travis (#32)
I think the way to approach this is to include the solr distribution in our repo
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-142441486.
averagehat commentedon Sep 22, 2015
Yes. Maybe hosting on S3 would be faster somehow too but putting it on the
repo is fine for now I think
On Tue, Sep 22, 2015 at 6:49 PM, Lianyi notifications@github.com wrote: