Steve Rowe commented on LUCENE-8106:

[~thetaphi]: I've run into trouble getting the script ^^ to work.  First, the 
local log isn't where it is on my Jenkins 
({{workspace/../builds/$BUILD_NUMBER/log}}, so I switched to fetching the log 
via HTTPS and storing it in a temp file.  That seems to work.  But now there 
are problems dealing with {{lucene.build.properties}}:


+ set -x
+ mktemp
+ TMPFILE=/tmp/tmp.GedGCMtTog
+ trap rm -f /tmp/tmp.GedGCMtTog EXIT
+ curl -o /tmp/tmp.GedGCMtTog 
+ grep --quiet reproduce with /tmp/tmp.GedGCMtTog
+ mv lucene/build lucene/build.orig
+ mv solr/build solr/build.orig
+ grep ^[[:space:]]*python32\.exe[[:space:]]*= 
+ cut -d= -f2
+ grep ^[[:space:]]*git\.exe[[:space:]]*= /home/jenkins/lucene.build.properties
+ cut -d= -f2
 -u dev-tools/scripts/reproduceJenkinsFailures.py --no-fetch 
/tmp/jenkins9073460340081845275.sh: 17: /tmp/jenkins9073460340081845275.sh: -u: 
not found
+ rm -f /tmp/tmp.GedGCMtTog

>From ^^, it looks to me like {{/home/jenkins/lucene.build.properties}} either 
>doesn't exist, or doesn't have entries for {{git.exe}} and {{python32.exe}}.  
>I apparently no longer have login access to the VMs (I tried).

> 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.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

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

Reply via email to