[
https://issues.apache.org/jira/browse/LUCENE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366831#comment-16366831
]
Uwe Schindler commented on LUCENE-8106:
---------------------------------------
Hi,
it might work out of box on the master slave, as it's running linux, but
definitely not on the others.
In general this Jenkins does not use native operating system's GIT at all, it
uses Jenkins JGIT plugin to handle checkouts. So git is not available on the
slaves with operating systems != linux. Python is available, but requires the
entries in lucene.build.xml properties file, as on the other operating systems
this is not in "PATH". That's the way how it's also setup on ASF jenkins.
I'd like to make the Jenkins build as generic as possible, so everything is
configured per node in lucene.build.properties, so the scriupt should read it
like the main jenkins.
IMHO, I'd add a top-level jenkins job that runs the python script (similar to
the smoke tester) using the standardized build properties, so it des not
require separate per-node-config:
{noformat}
$ ant run-jenkins-repro
{noformat}
This won't solve the missing "git" command problem.
Uwe
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
