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

Uwe Schindler edited comment on LUCENE-8106 at 2/23/18 7:51 AM:
----------------------------------------------------------------

bq. Powershell is now there! I think the biggest problem on Windows is also to 
read the properties file, as it uses escaping for backslashes  I am thinking 
about a better solution here. Unfortunately you can't add Python as a "Tool" so 
you can use "Tools Environment" to add a variable. Digging about that...

I have a solution: You can set environment variables per node in Jenkins 
config. I would just set a variable PYTHON3_EXE and remove the cryptic greps on 
lucene.build.properties.


was (Author: thetaphi):
bq. Powershell is now there! I think the biggest problem on Windows is also to 
read the properties file, as it uses escaping for backslashes  I am thinking 
about a better solution here. Unfortunately you can't add Python as a "Tool" so 
you can use "Tools Environment" to add a variable. Digging about that...

I have a solution: You can set environment variables per node in Jenkins 
config. I would just set a variable PYTHON3_EXECUTABLE and remove the cryptic 
greps on lucene.build.properties.

> Add script to attempt to reproduce failing tests from a Jenkins log
> -------------------------------------------------------------------
>
>                 Key: LUCENE-8106
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8106
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Major
>             Fix For: master (8.0), 7.3
>
>         Attachments: LUCENE-8106-part2.patch, LUCENE-8106-part3.patch, 
> LUCENE-8106.patch, LUCENE-8106.patch
>
>
> This script will be runnable from a downstream job triggered by an upstream 
> failing Jenkins job, passing log location info between the two.
> The script will also be runnable manually from a developer's cmdline.
> From the script help:
> {noformat}
> Usage:
>      python3 -u reproduceJenkinsFailures.py URL
> Must be run from a Lucene/Solr git workspace. Downloads the Jenkins
> log pointed to by the given URL, parses it for Git revision and failed
> Lucene/Solr tests, checks out the Git revision in the local workspace,
> groups the failed tests by module, then runs
> 'ant test -Dtest.dups=5 -Dtests.class="*.test1[|*.test2[...]]" ...'
> in each module of interest, failing at the end if any of the runs fails.
> To control the maximum number of concurrent JVMs used for each module's
> test run, set 'tests.jvms', e.g. in ~/lucene.build.properties
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to