You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (Created) (JIRA)" <ji...@apache.org> on 2012/03/22 14:40:22 UTC
[jira] [Created] (SOLR-3265) TestSolrEntityProcessorEndToEnd fails
if you have a running Solr instance
TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
-------------------------------------------------------------------------
Key: SOLR-3265
URL: https://issues.apache.org/jira/browse/SOLR-3265
Project: Solr
Issue Type: Test
Affects Versions: 3.6, 4.0
Reporter: Erick Erickson
Assignee: Erick Erickson
Priority: Minor
When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: [jira] [Commented] (SOLR-3265) TestSolrEntityProcessorEndToEnd
fails if you have a running Solr instance
Posted by Martijn v Groningen <ma...@gmail.com>.
:-) If I run the tests on my personal macbook it also takes a very very
very long time to complete. This macbook is 5 years old... Luckily I do
have another faster machine.
On 22 March 2012 15:00, Erick Erickson <er...@gmail.com> wrote:
> No, I have an OS X about 3 years old..... Sometimes in only feels like
> a 386 <G>...
>
> On Thu, Mar 22, 2012 at 9:56 AM, Robert Muir (Commented) (JIRA)
> <ji...@apache.org> wrote:
> >
> > [
> https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235581#comment-13235581]
> >
> > Robert Muir commented on SOLR-3265:
> > -----------------------------------
> >
> > {quote}
> > especially as 3.x "ant test" is taking 50+ minutes
> > {quote}
> >
> > Erick do you have a 386?
> >
> >> TestSolrEntityProcessorEndToEnd fails if you have a running Solr
> instance
> >>
> -------------------------------------------------------------------------
> >>
> >> Key: SOLR-3265
> >> URL: https://issues.apache.org/jira/browse/SOLR-3265
> >> Project: Solr
> >> Issue Type: Test
> >> Affects Versions: 3.6, 4.0
> >> Reporter: Erick Erickson
> >> Assignee: Erick Erickson
> >> Priority: Minor
> >>
> >> When running "ant test" from the command line in 3.x, if you have a
> Solr server running then TestSolrentityProcessorEndToEnd fails since it
> uses the default port (stack trace with "address already in use"). This
> should use some other port, especially as 3.x "ant test" is taking 50+
> minutes and I often open up a server to look at something else.
> >> In 4.0, some of the cloud tests also use 8983 as a port. Should these
> be changed too?
> >> And just to make my life *especially* interesting, at least one test
> puts the string "8983" in a document, which doesn't have to be changed
> <G>...
> >> Of course one can start your local server on a different port, but this
> seems trappy.
> >
> > --
> > This message is automatically generated by JIRA.
> > If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
--
Met vriendelijke groet,
Martijn van Groningen
Re: [jira] [Commented] (SOLR-3265) TestSolrEntityProcessorEndToEnd
fails if you have a running Solr instance
Posted by Erick Erickson <er...@gmail.com>.
No, I have an OS X about 3 years old..... Sometimes in only feels like
a 386 <G>...
On Thu, Mar 22, 2012 at 9:56 AM, Robert Muir (Commented) (JIRA)
<ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235581#comment-13235581 ]
>
> Robert Muir commented on SOLR-3265:
> -----------------------------------
>
> {quote}
> especially as 3.x "ant test" is taking 50+ minutes
> {quote}
>
> Erick do you have a 386?
>
>> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
>> -------------------------------------------------------------------------
>>
>> Key: SOLR-3265
>> URL: https://issues.apache.org/jira/browse/SOLR-3265
>> Project: Solr
>> Issue Type: Test
>> Affects Versions: 3.6, 4.0
>> Reporter: Erick Erickson
>> Assignee: Erick Erickson
>> Priority: Minor
>>
>> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
>> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
>> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
>> Of course one can start your local server on a different port, but this seems trappy.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3265) TestSolrEntityProcessorEndToEnd
fails if you have a running Solr instance
Posted by "Martijn van Groningen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235580#comment-13235580 ]
Martijn van Groningen commented on SOLR-3265:
---------------------------------------------
This is trappy! This should be changed.
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6, 4.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3265) TestSolrEntityProcessorEndToEnd
fails if you have a running Solr instance
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235581#comment-13235581 ]
Robert Muir commented on SOLR-3265:
-----------------------------------
{quote}
especially as 3.x "ant test" is taking 50+ minutes
{quote}
Erick do you have a 386?
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6, 4.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3265) TestSolrEntityProcessorEndToEnd fails
if you have a running Solr instance
Posted by "Erick Erickson (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson updated SOLR-3265:
---------------------------------
Affects Version/s: (was: 4.0)
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Fix For: 3.6
>
> Attachments: SOLR-3265.patch
>
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3265) TestSolrEntityProcessorEndToEnd fails
if you have a running Solr instance
Posted by "Luca Cavanna (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luca Cavanna updated SOLR-3265:
-------------------------------
Attachment: SOLR-3265.patch
Patch against 3.x branch to solve the TestSolrEntityProcessorEndToEnd port problem.
Trunk is already ok.
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6, 4.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Attachments: SOLR-3265.patch
>
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3265) TestSolrEntityProcessorEndToEnd fails
if you have a running Solr instance
Posted by "Erick Erickson (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved SOLR-3265.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.6
Fixed in 3x, r: 1304045
Didn't need to be fixed in trunk
Thanks Luca! I hadn't even had a chance to _begin_ looking at it before you fixed it!
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Fix For: 3.6
>
> Attachments: SOLR-3265.patch
>
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3265) TestSolrEntityProcessorEndToEnd
fails if you have a running Solr instance
Posted by "Luca Cavanna (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235642#comment-13235642 ]
Luca Cavanna commented on SOLR-3265:
------------------------------------
Looks like this has already been fixed on trunk some time ago. Erick, if you haven't started yet working on this I can provide a patch for 3x soon.
> TestSolrEntityProcessorEndToEnd fails if you have a running Solr instance
> -------------------------------------------------------------------------
>
> Key: SOLR-3265
> URL: https://issues.apache.org/jira/browse/SOLR-3265
> Project: Solr
> Issue Type: Test
> Affects Versions: 3.6, 4.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
>
> When running "ant test" from the command line in 3.x, if you have a Solr server running then TestSolrentityProcessorEndToEnd fails since it uses the default port (stack trace with "address already in use"). This should use some other port, especially as 3.x "ant test" is taking 50+ minutes and I often open up a server to look at something else.
> In 4.0, some of the cloud tests also use 8983 as a port. Should these be changed too?
> And just to make my life *especially* interesting, at least one test puts the string "8983" in a document, which doesn't have to be changed <G>...
> Of course one can start your local server on a different port, but this seems trappy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org