[
https://issues.apache.org/jira/browse/LUCENE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369834#comment-16369834
]
Uwe Schindler edited comment on LUCENE-8106 at 2/20/18 9:16 AM:
----------------------------------------------------------------
On Linux, they don't have entries for those tools, so it falls back to
build.xml's default behaviour. git.exe is undefined everywhere - except the
master Jenkins (Linux), which has GIT, but no other slave machine has GIT
installed. They only use Jenkins' internal JGit client, no command line. There
is no need to have Git for running Lucene builds (except packaging and jar
version numbers, but Policeman does not use this - because it's optional for
test builds).
{noformat}
jenkins@serv1:~$ pwd
/home/jenkins
jenkins@serv1:~$ cat lucene.build.properties
tests.jvms=3
tests.multiplier=3
{noformat}
FYI, on Windows it looks like that:
{noformat}
C:\Users\jenkins>type lucene.build.properties
python32.exe=C:\\Python35\\python.exe
perl.exe=C:\\Perl64\\bin\\perl.exe
tests.jvms=2
C:\Users\jenkins>git
'git' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
Same on MacOSX and Solaris.
Sorry for not being responsive, I am a bit busy today. Can you send me your SSH
key privately? I will put them on all 4 machines into jenkins home dir.
was (Author: thetaphi):
On Linux, they don't have entries for those tools, so it falls back to
build.xml's default behaviour. git.exe is undefined everywhere as except the
master Jenkins (Linux) no slave machine has GIT installed. They only use
Jenkins' internal JGit client, no command line.
{noformat}
jenkins@serv1:~$ pwd
/home/jenkins
jenkins@serv1:~$ cat lucene.build.properties
tests.jvms=3
tests.multiplier=3
{noformat}
FYI, on Windows it looks like that:
{noformat}
C:\Users\jenkins>type lucene.build.properties
python32.exe=C:\\Python35\\python.exe
perl.exe=C:\\Perl64\\bin\\perl.exe
tests.jvms=2
C:\Users\jenkins>git
'git' is not recognized as an internal or external command,
operable program or batch file.
{noformat}
Same on MacOSX and Solaris.
Sorry for not being responsive, I am a bit busy today. Can you send me your SSH
key privately? I will put them on all 4 machines into jenkins home dir.
> 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
