[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-11-10 Thread Timothy Potter (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205231#comment-14205231
 ] 

Timothy Potter commented on SOLR-6474:
--

Unfortunately, I think we're stuck with the script doing this is steps vs. 
using solr -e because -e relies on launching Solr in the background (so it can 
run other tasks after starting Solr) and the smoke tester works better if Solr 
is launched in the foreground with -f. 

I actually like the fact that the steps of starting, create core, index docs, 
query are broken out into specific steps because it helps with troubleshooting. 

Also, {{ %SOLR_TIP%/example/exampledocs/post.jar }} is still valid with the new 
layout as I didn't change the exampledocs directory at all.

> Smoke tester should use the Solr start scripts to start Solr
> 
>
> Key: SOLR-6474
> URL: https://issues.apache.org/jira/browse/SOLR-6474
> Project: Solr
>  Issue Type: Task
>  Components: scripts and tools
>Reporter: Shalin Shekhar Mangar
>  Labels: difficulty-easy, impact-low
> Fix For: 5.0
>
> Attachments: SOLR-6474-smoke_trunk_6.0.0.log, SOLR-6474.patch
>
>
> We should use the Solr bin scripts created by SOLR-3617 in the smoke tester 
> to test Solr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-11-07 Thread Anurag Sharma (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202323#comment-14202323
 ] 

Anurag Sharma commented on SOLR-6474:
-

Summarizing the issue I've faced while running smoke Tester.

First I was running it using Python-27 and seen SyntaxError issues and got rid 
of them when tried with Python 3.4.2.
Further, seen below error when tried to run smoke using :
{noformat}
python -u smokeTestRelease.py 
http://people.apache.org/~mikemccand/staging_area/lucene-solr-4.10.2-RC1-rev1634293
{noformat}

{code}
Java 1.7 JAVA_HOME=C:\Program Files\Java\jdk1.7.0_51
Traceback (most recent call last):
  File "smokeTestRelease.py", line 1522, in 
main()
  File "smokeTestRelease.py", line 1465, in main
c = parse_config()
  File "smokeTestRelease.py", line 1351, in parse_config
c.java = make_java_config(parser, c.test_java8)
  File "smokeTestRelease.py", line 1303, in make_java_config
run_java7 = _make_runner(java7_home, '1.7')
  File "smokeTestRelease.py", line 1294, in _make_runner
shell=True, stderr=subprocess.STDOUT).decode('utf-8')
  File "C:\Program Files (x86)\Python34\lib\subprocess.py", line 620, in 
check_output
raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command 'export JAVA_HOME="C:\Program 
Files\Java\jdk1.7.0_51" PATH="C:\Program Files\Java\jdk1.7.0_51/bin:$PATH" 
JAVACMD="C:\Program Files\Java\jdk1.7.0_51/bin/java"; java -version' returned 
non-zero exit status 1
{code}
The only usage example I find in the code is it takes a URL param and it's 
giving the above error:
{noformat}
Example usage:
python3.2 -u dev-tools/scripts/smokeTestRelease.py 
http://people.apache.org/~whoever/staging_area/lucene-solr-4.3.0-RC1-rev1469340
{noformat}

Shawn Heisey's {anchor:apa...@elyograg.org} observation:
When running that exact command on the tags/lucene_solr_4_10_2 checkout, it 
fails.  I think there must be something in the configuration that still says 
4.10.1:
{code}
prepare-release-no-sign:
[mkdir] Created dir:
/home/elyograg/asf/lucene_solr_4_10_2/lucene/build/fakeRelease
 [copy] Copying 431 files to
/home/elyograg/asf/lucene_solr_4_10_2/lucene/build/fakeRelease/lucene
 [copy] Copying 239 files to
/home/elyograg/asf/lucene_solr_4_10_2/lucene/build/fakeRelease/solr
 [exec] JAVA7_HOME is /usr/lib/jvm/java-7-oracle
 [exec] Traceback (most recent call last):
 [exec]   File
"/home/elyograg/asf/lucene_solr_4_10_2/dev-tools/scripts/smokeTestRelease.py",
line 1467, in 
 [exec] main()
 [exec]   File
"/home/elyograg/asf/lucene_solr_4_10_2/dev-tools/scripts/smokeTestRelease.py",
line 1308, in main
 [exec] smokeTest(baseURL, svnRevision, version, tmpDir,
isSigned, testArgs)
 [exec]   File
"/home/elyograg/asf/lucene_solr_4_10_2/dev-tools/scripts/smokeTestRelease.py",
line 1446, in smokeTest
 [exec] checkSigs('lucene', lucenePath, version, tmpDir, isSigned)
 [exec]   File
"/home/elyograg/asf/lucene_solr_4_10_2/dev-tools/scripts/smokeTestRelease.py",
line 359, in checkSigs
 [exec] raise RuntimeError('%s: unknown artifact %s: expected
prefix %s' % (project, text, expected))
 [exec] RuntimeError: lucene: unknown artifact
lucene-4.10.2-src.tgz: expected prefix lucene-4.10.1
 [exec] NOTE: output encoding is UTF-8
 [exec]
 [exec] Load release URL
"file:/home/elyograg/asf/lucene_solr_4_10_2/lucene/build/fakeRelease/"...
 [exec]
 [exec] Test Lucene...
 [exec]   test basics...
{code}


* Some Run using ant:
{code}
$ ant nightly-smoke -Dversion=6.0.0
Buildfile: C:\work\trunk\build.xml

clean:

clean:

clean:

-nightly-smoke-java8params:

nightly-smoke:

BUILD FAILED
C:\work\trunk\build.xml:392: Execute failed: java.io.IOException: Cannot run 
program "python3.2": CreateProcess error=2, The system cannot find the file 
specified
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at java.lang.Runtime.exec(Runtime.java:617)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:41)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:428)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:442)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:628)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:495)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.t

[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-10-17 Thread Anurag Sharma (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175879#comment-14175879
 ] 

Anurag Sharma commented on SOLR-6474:
-

This is lucene smoke test or solr? 
Other the smoke tester, how about updating all the references of starting solr 
"java -jar start.jar" with start script  in SOLR-3617?

> Smoke tester should use the Solr start scripts to start Solr
> 
>
> Key: SOLR-6474
> URL: https://issues.apache.org/jira/browse/SOLR-6474
> Project: Solr
>  Issue Type: Task
>  Components: scripts and tools
>Reporter: Shalin Shekhar Mangar
>  Labels: difficulty-easy, impact-low
> Fix For: 5.0
>
>
> We should use the Solr bin scripts created by SOLR-3617 in the smoke tester 
> to test Solr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-10-16 Thread Hoss Man (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174770#comment-14174770
 ] 

Hoss Man commented on SOLR-6474:


https://svn.apache.org/repos/asf/lucene/dev/trunk/dev-tools/scripts/smokeTestRelease.py

> Smoke tester should use the Solr start scripts to start Solr
> 
>
> Key: SOLR-6474
> URL: https://issues.apache.org/jira/browse/SOLR-6474
> Project: Solr
>  Issue Type: Task
>  Components: scripts and tools
>Reporter: Shalin Shekhar Mangar
>  Labels: difficulty-easy, impact-low
> Fix For: 5.0
>
>
> We should use the Solr bin scripts created by SOLR-3617 in the smoke tester 
> to test Solr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-10-16 Thread Anurag Sharma (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174692#comment-14174692
 ] 

Anurag Sharma commented on SOLR-6474:
-

Can you point the location of smoke tester.

> Smoke tester should use the Solr start scripts to start Solr
> 
>
> Key: SOLR-6474
> URL: https://issues.apache.org/jira/browse/SOLR-6474
> Project: Solr
>  Issue Type: Task
>  Components: scripts and tools
>Reporter: Shalin Shekhar Mangar
>  Labels: difficulty-easy, impact-low
> Fix For: 5.0
>
>
> We should use the Solr bin scripts created by SOLR-3617 in the smoke tester 
> to test Solr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org